You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/overview-managed-identity.md
+24-14Lines changed: 24 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -10,25 +10,22 @@ ms.service: app-service
10
10
ms.tgt_pltfrm: na
11
11
ms.devlang: multiple
12
12
ms.topic: article
13
-
ms.date: 11/20/2018
13
+
ms.date: 08/15/2019
14
14
ms.author: mahender
15
15
ms.reviewer: yevbronsh
16
16
17
17
---
18
18
19
19
# How to use managed identities for App Service and Azure Functions
20
20
21
-
> [!NOTE]
22
-
> Managed identity support for App Service on Linux and Web App for Containers is currently in preview.
23
-
24
21
> [!Important]
25
22
> Managed identities for App Service and Azure Functions will not behave as expected if your app is migrated across subscriptions/tenants. The app will need to obtain a new identity, which can be done by disabling and re-enabling the feature. See [Removing an identity](#remove) below. Downstream resources will also need to have access policies updated to use the new identity.
26
23
27
24
This topic shows you how to create a managed identity for App Service and Azure Functions applications and how to use it to access other resources. A managed identity from Azure Active Directory allows your app to easily access other AAD-protected resources such as Azure Key Vault. The identity is managed by the Azure platform and does not require you to provision or rotate any secrets. For more about managed identities in AAD, see [Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md).
28
25
29
26
Your application can be granted two types of identities:
30
-
- A **system-assigned identity** is tied to your application and is deleted if your app is deleted. An app can only have one system-assigned identity. System-assigned identity support is generally available for Windows apps.
31
-
- A **user-assigned identity** is a standalone Azure resource which can be assigned to your app. An app can have multiple user-assigned identities. User-assigned identity support is in preview for all app types.
27
+
- A **system-assigned identity** is tied to your application and is deleted if your app is deleted. An app can only have one system-assigned identity.
28
+
- A **user-assigned identity** is a standalone Azure resource which can be assigned to your app. An app can have multiple user-assigned identities.
32
29
33
30
## Adding a system-assigned identity
34
31
@@ -155,18 +152,12 @@ When the site is created, it has the following additional properties:
155
152
Where `<TENANTID>` and `<PRINCIPALID>` are replaced with GUIDs. The tenantId property identifies what AAD tenant the identity belongs to. The principalId is a unique identifier for the application's new identity. Within AAD, the service principal has the same name that you gave to your App Service or Azure Functions instance.
156
153
157
154
158
-
## Adding a user-assigned identity (preview)
159
-
160
-
> [!NOTE]
161
-
> User-assigned identities are currently in preview. Sovereign clouds are not yet supported.
155
+
## Adding a user-assigned identity
162
156
163
157
Creating an app with a user-assigned identity requires that you create the identity and then add its resource identifier to your app config.
164
158
165
159
### Using the Azure portal
166
160
167
-
> [!NOTE]
168
-
> This portal experience is being deployed and may not yet be available in all regions.
169
-
170
161
First, you'll need to create a user-assigned identity resource.
171
162
172
163
1. Create a user-assigned managed identity resource according to [these instructions](../active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-portal.md#create-a-user-assigned-managed-identity).
@@ -177,7 +168,7 @@ First, you'll need to create a user-assigned identity resource.
177
168
178
169
4. Select **Managed identity**.
179
170
180
-
5. Within the **User assigned (preview)** tab, click **Add**.
171
+
5. Within the **User assigned** tab, click **Add**.
181
172
182
173
6. Search for the identity you created earlier and select it. Click **Add**.
0 commit comments