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/active-directory/managed-identities-azure-resources/how-to-view-managed-identity-service-principal-cli.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Step-by-step instructions for viewing the service principal of a ma
4
4
services: active-directory
5
5
documentationcenter: ''
6
6
author: barclayn
7
-
manager: karenhoran
7
+
manager: rkarlin
8
8
editor: ''
9
9
10
10
ms.service: active-directory
@@ -44,4 +44,4 @@ az ad sp list --display-name <Azure resource name>
44
44
45
45
## Next steps
46
46
47
-
For more information on managing Azure AD service principals using Azure CLI, see [az ad sp](/cli/azure/ad/sp).
47
+
For more information on managing Azure AD service principals, see [Azure CLI ad sp](/cli/azure/ad/sp).
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/how-to-view-managed-identity-service-principal-portal.md
# What are managed identities for Azure resources?
23
23
24
-
A common challenge for developers is the management of secrets, credentials, certificates, keys etc used to secure communication between services. Managed identities eliminate the need for developers to manage these credentials.
24
+
A common challenge for developers is the management of secrets, credentials, certificates, and keys used to secure communication between services. Managed identities eliminate the need for developers to manage these credentials.
25
25
26
26
While developers can securely store the secrets in [Azure Key Vault](../../key-vault/general/overview.md), services need a way to access Azure Key Vault. Managed identities provide an automatically managed identity in Azure Active Directory for applications to use when connecting to resources that support Azure Active Directory (Azure AD) authentication. Applications can use managed identities to obtain Azure AD tokens without having to manage any credentials.
27
27
28
28
The following video shows how you can use managed identities:</br>
Here are some of the benefits of using managed identities:
35
33
36
34
- You don't need to manage credentials. Credentials aren’t even accessible to you.
37
35
- You can use managed identities to authenticate to any resource that supports [Azure AD authentication](../authentication/overview-authentication.md), including your own applications.
38
-
- Managed identities can be used without any additional cost.
36
+
- Managed identities can be used at no extra cost.
39
37
40
38
> [!NOTE]
41
39
> Managed identities for Azure resources is the new name for the service formerly known as Managed Service Identity (MSI).
@@ -64,11 +62,12 @@ The following table shows the differences between the two types of managed ident
64
62
65
63
## How can I use managed identities for Azure resources?
66
64
67
-
For using Managed identities, you have should do the following:
65
+
You can use managed identities by following the steps below:
66
+
68
67
1. Create a managed identity in Azure. You can choose between system-assigned managed identity or user-assigned managed identity.
69
-
2.In case of user-assigned managed identity, assign the managed identity to the "source" Azure Resource, such as an Azure Logic App or an Azure Web App.
68
+
2.When working with a user-assigned managed identity, assign the managed identity to the "source" Azure Resource, such as an Azure Logic App or an Azure Web App.
70
69
3. Authorize the managed identity to have access to the "target" service.
71
-
4. Use the managed identity to perform access. For this, you can use the Azure SDK with the Azure.Identity library. Some "source" resources offer connectors that know how to use Managed identities for the connections. In that case you simply use the identity as a feature of that "source" resource.
70
+
4. Use the managed identity to access a resource. In this step, you can use the Azure SDK with the Azure.Identity library. Some "source" resources offer connectors that know how to use Managed identities for the connections. In that case, you use the identity as a feature of that "source" resource.
72
71
73
72
74
73
## What Azure services support the feature?<aname="which-azure-services-support-managed-identity"></a>
If your virtual machine scale set does not have a system-assigned managed identity and you want to remove all user-assigned managed identities from it, use the following command:
125
+
If your virtual machine scale set doesn't have a system-assigned managed identity and you want to remove all user-assigned managed identities from it, use the following command:
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-storage-sas.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,14 @@ description: Tutorial showing how to use a Linux VM system-assigned managed iden
4
4
services: active-directory
5
5
documentationcenter: ''
6
6
author: barclayn
7
-
manager: karenhoran
8
-
editor: daveba
7
+
manager: rkarlin
9
8
ms.custom: subject-rbac-steps
10
9
ms.service: active-directory
11
10
ms.subservice: msi
12
11
ms.topic: tutorial
13
12
ms.tgt_pltfrm: na
14
13
ms.workload: identity
15
-
ms.date: 02/17/2022
14
+
ms.date: 06/24/2022
16
15
ms.author: barclayn
17
16
ms.collection: M365-identity-device-management
18
17
---
@@ -225,7 +224,7 @@ Response:
225
224
226
225
## Next steps
227
226
228
-
In this tutorial, you learned how to use a Linux VM system-assigned managed identity to access Azure Storage using a SAS credential. To learn more about Azure Storage SAS see:
227
+
In this tutorial, you learned how to use a Linux VM system-assigned managed identity to access Azure Storage using a SAS credential. To learn more about Azure Storage SAS, see:
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/tutorial-vm-managed-identities-cosmos.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
title: Use managed identities from a virtual machine to access Cosmos DB
3
3
description: Learn how to use managed identities with Windows VMs using the Azure portal, CLI, PowerShell, Azure Resource Manager template
4
4
author: barclayn
5
-
manager: karenhoran
5
+
manager: rkarlin
6
6
ms.service: active-directory
7
7
ms.subservice: msi
8
8
ms.workload: integration
9
9
ms.topic: tutorial
10
-
ms.date: 01/11/2022
10
+
ms.date: 06/24/2022
11
11
ms.author: barclayn
12
12
ms.custom: ep-miar
13
13
ms.tool: azure-cli, azure-powershell
@@ -28,7 +28,7 @@ In this article, we set up a virtual machine to use managed identities to connec
28
28
29
29
## Create a resource group
30
30
31
-
Create a resource group called **mi-test**. We will use this resource group for all resources used in this tutorial.
31
+
Create a resource group called **mi-test**. We'll use this resource group for all resources used in this tutorial.
32
32
33
33
-[Create a resource group using the Azure portal](../../azure-resource-manager/management/manage-resource-groups-portal.md#create-resource-groups)
34
34
-[Create a resource group using the CLI](../../azure-resource-manager/management/manage-resource-groups-cli.md#create-resource-groups)
@@ -81,7 +81,7 @@ New-AzVm `
81
81
82
82
# [Azure CLI](#tab/azure-cli)
83
83
84
-
Create a VM using [az vm create](/cli/azure/vm/#az-vm-create). The following example creates a VM named *myVM* with a system-assigned managed identity, as requested by the `--assign-identity` parameter. The `--admin-username` and `--admin-password` parameters specify the administrative user name and password account for virtual machine sign-in. Update these values as appropriate for your environment:
84
+
Create a VM using [Azure CLI vm create command](/cli/azure/vm/#az-vm-create). The following example creates a VM named *myVM* with a system-assigned managed identity, as requested by the `--assign-identity` parameter. The `--admin-username` and `--admin-password` parameters specify the administrative user name and password account for virtual machine sign-in. Update these values as appropriate for your environment:
85
85
86
86
```azurecli-interactive
87
87
az vm create --resource-group myResourceGroup --name myVM --image win2016datacenter --generate-ssh-keys --assign-identity --admin-username azureuser --admin-password myPassword12
@@ -126,7 +126,7 @@ The steps below show you how to create a virtual machine with a user-assigned ma
126
126
127
127
# [Portal](#tab/azure-portal)
128
128
129
-
Today, the Azure portal does not support assigning a user-assigned managed identity during the creation of a VM. You should create a virtual machine and then assign a user assigned managed identity to it.
129
+
Today, the Azure portal doesn't support assigning a user-assigned managed identity during the creation of a VM. You should create a virtual machine and then assign a user assigned managed identity to it.
130
130
131
131
[Configure managed identities for Azure resources on a VM using the Azure portal](qs-configure-portal-windows-vm.md#user-assigned-managed-identity)
132
132
@@ -211,7 +211,7 @@ Under the resources element, add the following entry to assign a user-assigned m
211
211
212
212
## Create a Cosmos DB account
213
213
214
-
Now that we have a VM with either a user-assigned managed identity or a system-assigned managed identity we need a Cosmos DB account available where you have administrative rights. If you need to create a Cosmos DB account for this tutorial the [Cosmos DB quickstart](../..//cosmos-db/sql/create-cosmosdb-resources-portal.md) provides detailed steps on how to do that.
214
+
Now that we have a VM with either a user-assigned managed identity or a system-assigned managed identity we need a Cosmos DB account available where you have administrative rights. If you need to create a Cosmos DB account for this tutorial, the [Cosmos DB quickstart](../..//cosmos-db/sql/create-cosmosdb-resources-portal.md) provides detailed steps on how to do that.
215
215
216
216
>[!NOTE]
217
217
> Managed identities may be used to access any Azure resource that supports Azure Active Directory authentication. This tutorial assumes that your Cosmos DB account will be configured as shown below.
When the role assignment step completes, you should see results similar to the ones shown below.
261
261
262
-
:::image type="content" source="media/how-to-manage-identities-vm-cosmos/results-role-assignment.png" alt-text="This shows the results of the role assignment.":::
262
+
:::image type="content" source="media/how-to-manage-identities-vm-cosmos/results-role-assignment.png" alt-text="screenshot shows the results of the role assignment.":::
263
263
264
264
# [Azure CLI](#tab/azure-cli)
265
265
@@ -297,7 +297,7 @@ Getting access to Cosmos using managed identities may be achieved using the Azur
297
297
298
298
The ManagedIdentityCredential class attempts to authentication using a managed identity assigned to the deployment environment. The [DefaultAzureCredential](/dotnet/api/overview/azure/identity-readme) class goes through different authentication options in order. The second authentication option that DefaultAzureCredential attempts is Managed identities.
299
299
300
-
In the example shown below you create a database, a container, an item in the container, and read back the newly created item using the virtual machine's system assigned managed identity. If you want to use a user-assigned managed identity, you need to specify the user-assigned managed identity by specifying the managed identity's client ID.
300
+
In the example shown below, you create a database, a container, an item in the container, and read back the newly created item using the virtual machine's system assigned managed identity. If you want to use a user-assigned managed identity, you need to specify the user-assigned managed identity by specifying the managed identity's client ID.
0 commit comments