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/cloud-infrastructure-entitlement-management/product-statistical-anomalies.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ Statistical anomalies can detect outliers in an identity's behavior if recent ac
70
70
- The **Controller** column displays if the controller is enabled or disabled.
71
71
72
72
73
-
1.On the **Configuration** tab, to update the **Time Interval**, from the **Time Range** dropdown, select **90 Days**, **60 Days**, or **30 Days**, and then select**Save**.
# What is password hash synchronization with Azure AD?
16
-
Password hash synchronization is one of the sign-in methods used to accomplish hybrid identity. Azure AD Connect synchronizes a hash, of the hash, of a user's password from an on-premises Active Directory instance to a cloud-based Azure AD instance.
16
+
Password hash synchronization is one of the sign-in methods used to accomplish hybrid identity. Azure AD Connect synchronizes a hash of a user's password from an on-premises Active Directory instance to a cloud-based Azure AD instance.
17
17
18
18
Password hash synchronization is an extension to the directory synchronization feature implemented by Azure AD Connect sync. You can use this feature to sign in to Azure AD services like Microsoft 365. You sign in to the service by using the same password you use to sign in to your on-premises Active Directory instance.
Copy file name to clipboardExpand all lines: articles/active-directory/managed-identities-azure-resources/how-managed-identities-work-vm.md
+19-4Lines changed: 19 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.subservice: msi
12
12
ms.devlang:
13
13
ms.topic: conceptual
14
14
ms.custom: mvc
15
-
ms.date: 10/30/2022
15
+
ms.date: 11/15/2022
16
16
ms.author: barclayn
17
17
ms.collection: M365-identity-device-management
18
18
---
@@ -33,7 +33,7 @@ Your code can use a managed identity to request access tokens for services that
33
33
34
34
The following diagram shows how managed service identities work with Azure virtual machines (VMs):
35
35
36
-
[](media/how-managed-identities-work-vm/data-flow.png#lightbox)
36
+
[](media/how-managed-identities-work-vm/data-flow.png#lightbox)
37
37
38
38
The following table shows the differences between the system-assigned and user-assigned managed identities:
39
39
@@ -52,12 +52,18 @@ The following table shows the differences between the system-assigned and user-a
52
52
53
53
3. Azure Resource Manager updates the VM identity using the Azure Instance Metadata Service identity endpoint (for [Windows](/azure/virtual-machines/windows/instance-metadata-service) and [Linux](/azure/virtual-machines/linux/instance-metadata-service)), providing the endpoint with the service principal client ID and certificate.
54
54
55
-
4. After the VM has an identity, use the service principal information to grant the VM access to Azure resources. To call Azure Resource Manager, use Azure role-based access control (Azure RBAC) to assign the appropriate role to the VM service principal. To call Key Vault, grant your code access to the specific secret or key in Key Vault.
55
+
4. After the VM has an identity, use the service principal information to grant the VM access to Azure resources. To call Azure Resource Manager, use Azure Role-Based Access Control (Azure RBAC) to assign the appropriate role to the VM service principal. To call Key Vault, grant your code access to the specific secret or key in Key Vault.
56
56
57
57
5. Your code that's running on the VM can request a token from the Azure Instance Metadata service endpoint, accessible only from within the VM: `http://169.254.169.254/metadata/identity/oauth2/token`
58
58
- The resource parameter specifies the service to which the token is sent. To authenticate to Azure Resource Manager, use `resource=https://management.azure.com/`.
59
59
- API version parameter specifies the IMDS version, use api-version=2018-02-01 or greater.
60
60
61
+
The following example demonstrates how to to use CURL to make a request to the local Managed Identity endpoint to get an access token for Azure Instance Metadata service.
6. A call is made to Azure AD to request an access token (as specified in step 5) by using the client ID and certificate configured in step 3. Azure AD returns a JSON Web Token (JWT) access token.
62
68
63
69
7. Your code sends the access token on a call to a service that supports Azure AD authentication.
@@ -77,9 +83,18 @@ The following table shows the differences between the system-assigned and user-a
77
83
78
84
5. Your code that's running on the VM can request a token from the Azure Instance Metadata Service identity endpoint, accessible only from within the VM: `http://169.254.169.254/metadata/identity/oauth2/token`
79
85
- The resource parameter specifies the service to which the token is sent. To authenticate to Azure Resource Manager, use `resource=https://management.azure.com/`.
80
-
- The client ID parameter specifies the identity for which the token is requested. This value is required for disambiguation when more than one user-assigned identity is on a single VM.
86
+
- The `client_id` parameter specifies the identity forwhich the token is requested. This value is required for disambiguation when more than one user-assigned identity is on a single VM. You can find the **Client ID**in the Managed Identity **Overview**:
87
+
88
+
[](./media/how-managed-identities-work-vm/managed-identity-client-id.png#lightbox)
89
+
81
90
- The API version parameter specifies the Azure Instance Metadata Service version. Use `api-version=2018-02-01` or higher.
82
91
92
+
The following example demonstrates how to to use CURL to make a request to the local Managed Identity endpoint to get an access token for Azure Instance Metadata service.
6. A call is made to Azure AD to request an access token (as specified in step 5) by using the client ID and certificate configured in step 3. Azure AD returns a JSON Web Token (JWT) access token.
84
99
7. Your code sends the access token on a call to a service that supports Azure AD authentication.
Copy file name to clipboardExpand all lines: articles/active-directory/roles/admin-units-assign-roles.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
9
9
ms.topic: how-to
10
10
ms.subservice: roles
11
11
ms.workload: identity
12
-
ms.date: 07/15/2022
12
+
ms.date: 11/15/2022
13
13
ms.author: rolyon
14
14
ms.reviewer: anandy
15
15
ms.custom: oldportal;it-pro;
@@ -46,6 +46,7 @@ The following Azure AD roles can be assigned with administrative unit scope. Add
46
46
|[Helpdesk Administrator](permissions-reference.md#helpdesk-administrator)| Can reset passwords for non-administrators in the assigned administrative unit only. |
47
47
|[License Administrator](permissions-reference.md#license-administrator)| Can assign, remove, and update license assignments within the administrative unit only. |
48
48
|[Password Administrator](permissions-reference.md#password-administrator)| Can reset passwords for non-administrators within the assigned administrative unit only. |
49
+
|[Printer Administrator](permissions-reference.md#printer-administrator)| Can manage printers and printer connectors. For more information, see [Delegate administration of printers in Universal Print](/universal-print/portal/delegated-admin#scoped-admin-vs-tenant-printer-admin). |
49
50
|[SharePoint Administrator](permissions-reference.md#sharepoint-administrator)| Can manage Microsoft 365 groups in the assigned administrative unit only. For SharePoint sites associated with Microsoft 365 groups in an administrative unit, can also update site properties (site name, URL, and external sharing policy) using the Microsoft 365 admin center. Cannot use the SharePoint admin center or SharePoint APIs to manage sites. |
50
51
|[Teams Administrator](permissions-reference.md#teams-administrator)| Can manage Microsoft 365 groups in the assigned administrative unit only. Can manage team members in the Microsoft 365 admin center for teams associated with groups in the assigned administrative unit only. Cannot use the Teams admin center. |
51
52
|[Teams Devices Administrator](permissions-reference.md#teams-devices-administrator)| Can perform management related tasks on Teams certified devices. |
0 commit comments