An Azure service that automates the access and use of data across clouds without writing code.
Hi @Kate
Thank you for reaching out to Microsoft Q&A
Thank you for reaching out to Microsoft Q&A. Based on the information provided, the issue is not related to RBAC permissions, browser cache, or resource configuration, as these have already been validated from your end. The behavior where the Edit button is greyed out and the Logic App Designer keeps spinning typically occurs when the Azure portal designer is unable to fully load the workflow metadata from the backend. In such cases, the portal falls back to a read-only state, which disables editing. This can happen due to backend service issues, workflow definition problems, connector loading delays, or subscription/region-specific inconsistencies. Since the same workflows work in another subscription within the same tenant, this strongly indicates a subscription-specific or platform-side issue rather than a user-side configuration problem. Refer below points to resolve this issue or this is the workaround
1. Try accessing Code view directly
- Navigate to Logic App → Workflow → Code view
- If Code view also keeps loading (spinner), it confirms backend/designer initialization issue
- If it opens, try making a small change and save
2. Disable and re-enable the Logic App
- Go to Logic App → Overview → Click Disable
- Wait for a minute → Refresh portal → Open Designer again
- Sometimes active workflow state blocks designer loading
3. Validate workflow using CLI or export Try fetching workflow definition:
az logic workflow show --name <logicapp-name> --resource-group <resource-group>
- If this command fails or hangs → confirms backend/service issue
4. Create a new Logic App and import definition
- Create a new Logic App in same subscription
- Copy existing workflow JSON → paste into new Logic App
- If new Logic App works → issue is with existing workflow metadata
- If new Logic App also fails → subscription-level issue
5. Test in another region within same subscription
- Create a test Logic App in a different Azure region
- If it works → indicates region-specific backend issue
and click on Yes for was this answer helpful. And, if you have any further query do let us know.