Share via

Cannot edit consumption workflows

Kate 0 Reputation points
2026-06-11T06:05:23.8433333+00:00

Cannot edit consumption workflows. Button is greyed out. Occurring for both consumption logic apps created.

  1. No resource locks.
  2. Role: Contributor and Owner
  3. Tried deleting cache + cookies
  4. Tried incognito
  5. Resource Provider enabled
  6. Tried accessing through Development Tools dropdown - both "Logic App Designer" and "Logic App Code view" result in spinning wheel of loading
  7. Logic Apps working on other subscription on tenant.

Browser: Chrome

OS: Windows 11

Azure Logic Apps
Azure Logic Apps

An Azure service that automates the access and use of data across clouds without writing code.


2 answers

Sort by: Most helpful
  1. Siddhesh Desai 7,400 Reputation points Microsoft External Staff Moderator
    2026-06-11T08:59:46.32+00:00

    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

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-06-11T06:05:35.5133333+00:00

    For deployed Logic Apps (Consumption), the Azure portal designer is read-only. Editing must be done either:

    1. In Visual Studio Code using the Logic Apps (Consumption) extension, or
    2. By editing the workflow definition JSON directly (via VS Code) and uploading it.

    From the documented behavior:

    • A deployed Consumption workflow opened in the Azure portal designer is not editable.
    • In Visual Studio Code, a deployed Consumption workflow can be edited only in code view. If opened in the designer, it is read-only.

    To edit the workflows:

    1. Install Visual Studio Code and the Azure Logic Apps (Consumption) extension.
    2. In VS Code, open the Azure pane (Azure icon on the Activity Bar).
    3. Under Logic Apps (Consumption), expand the subscription and locate the logic app.
    4. Right‑click the logic app and select Open in Editor.
    5. Edit the JSON definition in <logic-app-name>.logicapp.json.
    6. Save; when prompted, choose Upload to publish changes to the deployed workflow.

    If the workflow is disabled, re‑enable it after publishing changes.

    If the portal continues to show a spinning wheel for the designer/code view, use VS Code as the primary editing experience for deployed Consumption workflows, as supported by the product.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.