Skip to content

Commit 8ab22f7

Browse files
authored
Merge pull request #218385 from MicrosoftDocs/main
Publish to live, Tuesday 4 AM PST, 11/15
2 parents e8b6a2d + 3d79f16 commit 8ab22f7

File tree

145 files changed

+2131
-708
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

145 files changed

+2131
-708
lines changed

articles/active-directory/cloud-infrastructure-entitlement-management/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Customers can right-size permissions based on usage, grant new permissions on-de
5555

5656
### Monitor
5757

58-
Customers can detect anomalous activities with machine language-powered (ML-powered) alerts and generate detailed forensic reports.
58+
Customers can detect anomalous activities with machine learning-powered (ML-powered) alerts and generate detailed forensic reports.
5959

6060
- ML-powered anomaly detections.
6161
- Context-rich forensic reports around identities, actions, and resources to support rapid investigation and remediation.

articles/active-directory/cloud-infrastructure-entitlement-management/product-permission-analytics.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,6 @@ This article describes how you can create and view permission analytics triggers
6161

6262
- The **Status** column displays if the authorization system is online or offline
6363
- The **Controller** column displays if the controller is enabled or disabled.
64-
65-
1. On the **Configuration** tab, to update the **Time Interval**, select **90 Days**, **60 Days**, or **30 Days** from the **Time range** dropdown.
6664
1. Select **Save**.
6765

6866
## View permission analytics alert triggers

articles/active-directory/cloud-infrastructure-entitlement-management/product-statistical-anomalies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Statistical anomalies can detect outliers in an identity's behavior if recent ac
7070
- The **Controller** column displays if the controller is enabled or disabled.
7171

7272

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**.
73+
1. Select **Save**.
7474

7575
## View statistical anomaly triggers
7676

articles/active-directory/hybrid/whatis-phs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.collection: M365-identity-device-management
1313
---
1414

1515
# 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.
1717

1818
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.
1919

articles/active-directory/managed-identities-azure-resources/how-managed-identities-work-vm.md

Lines changed: 19 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.subservice: msi
1212
ms.devlang:
1313
ms.topic: conceptual
1414
ms.custom: mvc
15-
ms.date: 10/30/2022
15+
ms.date: 11/15/2022
1616
ms.author: barclayn
1717
ms.collection: M365-identity-device-management
1818
---
@@ -33,7 +33,7 @@ Your code can use a managed identity to request access tokens for services that
3333

3434
The following diagram shows how managed service identities work with Azure virtual machines (VMs):
3535

36-
[![Managed service identities and Azure VMs](media/how-managed-identities-work-vm/data-flow.png)](media/how-managed-identities-work-vm/data-flow.png#lightbox)
36+
[![Diagram that shows how managed service identities are associated with Azure virtual machines, get an access token, and invoked a protected Azure AD resource.](media/how-managed-identities-work-vm/data-flow.png)](media/how-managed-identities-work-vm/data-flow.png#lightbox)
3737

3838
The following table shows the differences between the system-assigned and user-assigned managed identities:
3939

@@ -52,12 +52,18 @@ The following table shows the differences between the system-assigned and user-a
5252

5353
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.
5454

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.
5656

5757
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`
5858
- The resource parameter specifies the service to which the token is sent. To authenticate to Azure Resource Manager, use `resource=https://management.azure.com/`.
5959
- API version parameter specifies the IMDS version, use api-version=2018-02-01 or greater.
6060

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.
62+
63+
```bash
64+
curl 'http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https%3A%2F%2Fstorage.azure.com%2F' -H Metadata:true
65+
```
66+
6167
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.
6268

6369
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
7783
7884
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`
7985
- 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 for which 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+
[![Screenshot that shows how to copy the managed identity client ID.](./media/how-managed-identities-work-vm/managed-identity-client-id.png)](./media/how-managed-identities-work-vm/managed-identity-client-id.png#lightbox)
89+
8190
- The API version parameter specifies the Azure Instance Metadata Service version. Use `api-version=2018-02-01` or higher.
8291

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.
93+
94+
```bash
95+
curl 'http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https%3A%2F%2Fstorage.azure.com%2F&client_id=12345678-0000-0000-0000-000000000000' -H Metadata:true
96+
```
97+
8398
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.
8499
7. Your code sends the access token on a call to a service that supports Azure AD authentication.
85100

Loading

articles/active-directory/roles/admin-units-assign-roles.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.topic: how-to
1010
ms.subservice: roles
1111
ms.workload: identity
12-
ms.date: 07/15/2022
12+
ms.date: 11/15/2022
1313
ms.author: rolyon
1414
ms.reviewer: anandy
1515
ms.custom: oldportal;it-pro;
@@ -46,6 +46,7 @@ The following Azure AD roles can be assigned with administrative unit scope. Add
4646
| [Helpdesk Administrator](permissions-reference.md#helpdesk-administrator) | Can reset passwords for non-administrators in the assigned administrative unit only. |
4747
| [License Administrator](permissions-reference.md#license-administrator) | Can assign, remove, and update license assignments within the administrative unit only. |
4848
| [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). |
4950
| [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. |
5051
| [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. |
5152
| [Teams Devices Administrator](permissions-reference.md#teams-devices-administrator) | Can perform management related tasks on Teams certified devices. |
2.87 KB
Loading
2.78 KB
Loading
821 Bytes
Loading

0 commit comments

Comments
 (0)