Skip to content

Commit 75e0a43

Browse files
Merge pull request #303359 from snshivakumar/patch-5
Update LA Standard Create Page with new UX Auth Tab Steps
2 parents 10b134e + 437ad63 commit 75e0a43

File tree

3 files changed

+16
-1
lines changed

3 files changed

+16
-1
lines changed

articles/logic-apps/create-single-tenant-workflows-azure-portal.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.suite: integration
77
ms.reviewer: estfan, azla
88
ms.collection: ce-skilling-ai-copilot
99
ms.topic: how-to
10-
ms.date: 02/07/2025
10+
ms.date: 08/06/2025
1111
ms.update-cycle: 180-days
1212
# Customer intent: As a developer, I want to create my first example Standard logic app workflow that runs in single-tenant Azure Logic Apps using the Azure portal.
1313
---
@@ -195,6 +195,21 @@ For optimal designer responsiveness and performance, review and follow these gui
195195
1. On the **Monitoring** tab, under **Application Insights**, set **Enable Application Insights** to **Yes**.
196196

197197
1. For the **Application Insights** setting, either select an existing Application Insights instance, or if you want to create a new instance, select **Create new** and provide the name that you want to use.
198+
199+
1. On the **Authentication** tab, under **Authentication type**, select the authentication to use for connecting to the host storage account resource (**Host storage (AzureWebJobsStorage)**).
200+
201+
> [!IMPORTANT]
202+
>
203+
> If you select **Managed identity** for authentication, you must specify the managed identity to use. Choose one of the following options:
204+
>
205+
> - If you select **Create new managed identity**, the portal creates this identity and automatically assigns the correct role-based access
206+
> permissions to the identity on the host storage account for your logic app. After you create your logic app, you might have to wait a few
207+
> minutes for the permissions to propagate onto your new managed identity. You can then restart your logic app. If no option exists to create
208+
> a managed identity, you need the lowest level of permissions that permits you to complete this task.
209+
>
210+
> - If you select an existing managed identity, you must manually assign the roles in the **Minimum roles required column** to the managed
211+
> identity on the host storage account resource. Consider completing this assignment before you deploy your logic app. Otherwise, you get
212+
> errors when you open your new logic app resource. For more information, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
198213
199214
1. After Azure validates your logic app settings, on the **Review + create** tab, select **Create**, for example:
200215

38.6 KB
Loading
80.2 KB
Loading

0 commit comments

Comments
 (0)