Skip to content

Commit b8f2a89

Browse files
Stacyrch140Stacyrch140
authored
Merge pull request #252779 from alexbuckgit/alexbuckgit/docutune-autopr-20230925-215651-9188233-ignore-build
[BULK] - DocuTune - Cleanup pass for Microsoft Entra rebrand (part 6)
2 parents cda34e4 + e80c338 commit b8f2a89

25 files changed

+100
-86
lines changed

‎articles/active-directory/manage-apps/migrate-okta-sign-on-policies-conditional-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ Before you convert to Conditional Access, confirm the base MFA tenant settings f
133133

134134
![Screenshot of the multifactor authentication screen.](media/migrate-okta-sign-on-policies-conditional-access/legacy-portal.png)
135135

136-
5. Confirm there are no users enabled for legacy MFA: On the **multifactor authentication** menu, on **multifactor authentication status**, select **Enabled** and **Enforced**. If the tenant has users in the following views, disable them in the legacy menu.
136+
5. Confirm there are no users enabled for legacy MFA: On the **Multifactor authentication** menu, on **Multifactor authentication status**, select **Enabled** and **Enforced**. If the tenant has users in the following views, disable them in the legacy menu.
137137

138138
![Screenshot of the multifactor authentication screen with the search feature highlighted.](media/migrate-okta-sign-on-policies-conditional-access/disable-user-portal.png)
139139

‎articles/active-directory/manage-apps/migrate-okta-sync-provisioning.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ You can connect to Microsoft Graph PowerShell and examine the current ImmutableI
4848
`Install-Module AzureAD` in an administrative session before you run the following commands:
4949

5050
```Powershell
51-
Import-module AzureAD
51+
Import-Module AzureAD
5252
Connect-MgGraph
5353
```
5454

@@ -120,7 +120,7 @@ After you prepare your list of source and destination targets, install a Microso
120120

121121
1. Download and install Microsoft Entra Connect on a server. See, [Custom installation of Microsoft Entra Connect](../hybrid/connect/how-to-connect-install-custom.md).
122122
2. In the left panel, select **Identifying users**.
123-
3. On the **Uniquely identifying your users** page, under **Select how users should be identified with Azure AD**, select **Choose a specific attribute**.
123+
3. On the **Uniquely identifying your users** page, under **Select how users should be identified with Microsoft Entra ID**, select **Choose a specific attribute**.
124124
4. If you haven't modified the Okta default, select **mS-DS-ConsistencyGUID**.
125125

126126
>[!WARNING]
@@ -274,5 +274,5 @@ After you disable Okta provisioning, the Microsoft Entra cloud sync agent can sy
274274
## Next steps
275275

276276
- [Tutorial: Migrate your applications from Okta to Microsoft Entra ID](migrate-applications-from-okta.md)
277-
- [Tutorial: Migrate Okta federation to Microsoft Entra managed authentication](migrate-okta-federation.md)
277+
- [Tutorial: Migrate Okta federation to Microsoft Entra ID managed authentication](migrate-okta-federation.md)
278278
- [Tutorial: Migrate Okta sign-on policies to Microsoft Entra Conditional Access](./migrate-okta-sign-on-policies-conditional-access.md)

‎articles/active-directory/manage-apps/silverfort-integration.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ ms.custom: not-enterprise-apps
1818

1919
[Silverfort](https://www.silverfort.com/) uses agent-less and proxy-less technology to connect your assets on-premises and in the cloud to Microsoft Entra ID. This solution enables organizations to apply identity protection, visibility, and user experience across environments in Microsoft Entra ID. It enables universal risk-based monitoring and assessment of authentication activity for on-premises and cloud environments, and helps to prevent threats.
2020

21+
<!-- docutune:ignore "Azure A ?D" -->
22+
2123
In this tutorial, learn how to integrate your on-premises Silverfort implementation with Microsoft Entra ID.
2224

2325
Learn more: [Microsoft Entra hybrid joined devices](../devices/concept-hybrid-join.md).
@@ -75,7 +77,7 @@ Set up Silverfort Azure AD Adapter in your Microsoft Entra tenant:
7577
4. Select **Save Changes**.
7678
5. On the **Permissions requested** dialog, select **Accept**.
7779

78-
![image shows Microsoft Entra bridge connector](./media/silverfort-integration/bridge-connector.png)
80+
![image shows Azure A D bridge connector](./media/silverfort-integration/bridge-connector.png)
7981

8082
![image shows registration confirmation](./media/silverfort-integration/grant-permission.png)
8183

@@ -85,7 +87,7 @@ Set up Silverfort Azure AD Adapter in your Microsoft Entra tenant:
8587

8688
7. On the **Settings** page, select **Save Changes**.
8789

88-
![image shows the Azure AD Adapter](./media/silverfort-integration/silverfort-adapter.png)
90+
![image shows the Azure A D Adapter](./media/silverfort-integration/silverfort-adapter.png)
8991

9092
8. Sign in to your Microsoft Entra account. In the left pane, select **Enterprise applications**. The **Silverfort Azure AD Adapter** application appears as registered.
9193

@@ -120,7 +122,7 @@ Set up Silverfort Azure AD Adapter in your Microsoft Entra tenant:
120122

121123
17. For Action, select **Azure AD BRIDGE**.
122124

123-
![image shows save Azure AD bridge](./media/silverfort-integration/save-bridge.png)
125+
![image shows save Azure A D bridge](./media/silverfort-integration/save-bridge.png)
124126

125127
18. Select **Save**. You're prompted to turn on the policy.
126128

‎articles/active-directory/managed-identities-azure-resources/msi-tutorial-linux-vm-access-arm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ To complete these steps, you need an SSH client. If you are using Windows, you c
123123
```
124124

125125
> [!NOTE]
126-
> The value of the `resource` parameter must be an exact match for what is expected by Azure AD. When using the Resource Manager resource ID, you must include the trailing slash on the URI. 
126+
> The value of the `resource` parameter must be an exact match for what is expected by Microsoft Entra ID. When using the Resource Manager resource ID, you must include the trailing slash on the URI. 
127127
128128
The response includes the access token you need to access Azure Resource Manager. 
129129

‎articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-arm.md

Lines changed: 53 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -58,51 +58,63 @@ When you use managed identities for Azure resources, your code can get access to
5858

5959
To complete these steps, you need an SSH client. If you're using Windows, you can use the SSH client in the [Windows Subsystem for Linux](/windows/wsl/about). If you need assistance configuring your SSH client's keys, see [How to Use SSH keys with Windows on Azure](../../virtual-machines/linux/ssh-from-windows.md), or [How to create and use an SSH public and private key pair for Linux VMs in Azure](../../virtual-machines/linux/mac-create-ssh-keys.md).
6060

61-
1. In the portal, navigate to your Linux VM and in the **Overview**, select **Connect**.  
62-
2. **Connect** to the VM with the SSH client of your choice. 
63-
3. In the terminal window, using `curl`, make a request to the local managed identities for Azure resources endpoint to get an access token for Azure Resource Manager.  
61+
1. In the portal, navigate to your Linux VM and in the **Overview**, select **Connect**.
62+
63+
2. **Connect** to the VM with the SSH client of your choice.
64+
65+
3. In the terminal window, using `curl`, make a request to the local managed identities for Azure resources endpoint to get an access token for Azure Resource Manager.
66+
 
67+
The `curl` request for the access token is below.
68+
69+
```bash
70+
curl 'http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/' -H Metadata:true
71+
```
72+
73+
> [!NOTE]
74+
> The value of the `resource` parameter must be an exact match for what is expected by Microsoft Entra ID. In the case of the Resource Manager resource ID, you must include the trailing slash on the URI.
75+
76+
The response includes the access token you need to access Azure Resource Manager.
77+
78+
Response:
79+
80+
```json
81+
{
82+
"access_token":"eyJ0eXAiOi...",
83+
"refresh_token":"",
84+
"expires_in":"3599",
85+
"expires_on":"1504130527",
86+
"not_before":"1504126627",
87+
"resource":"https://management.azure.com",
88+
"token_type":"Bearer"
89+
}
90+
```
91+
92+
You can use this access token to access Azure Resource Manager, for example to read the details of the Resource Group to which you previously granted this VM access. Replace the values of `<SUBSCRIPTION-ID>`, `<RESOURCE-GROUP>`, and `<ACCESS-TOKEN>` with the ones you created earlier.
93+
94+
> [!NOTE]
95+
> The URL is case-sensitive, so ensure if you are using the exact same case as you used earlier when you named the Resource Group, and the uppercase “G” in “resourceGroup”.  
96+
97+
```bash
98+
curl https://management.azure.com/subscriptions/<SUBSCRIPTION-ID>/resourceGroups/<RESOURCE-GROUP>?api-version=2016-09-01 -H "Authorization: Bearer <ACCESS-TOKEN>" 
99+
```
100+
101+
The response back with the specific Resource Group information:
64102

65-
The `curl` request for the access token is below.  
66-
67-
```bash
68-
curl 'http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/' -H Metadata:true   
69-
```
70-
71-
> [!NOTE]
72-
> The value of the “resource” parameter must be an exact match for what is expected by Azure AD.  In the case of the Resource Manager resource ID, you must include the trailing slash on the URI. 
73-
74-
The response includes the access token you need to access Azure Resource Manager. 
75-
76-
Response:  
77-
78-
```bash
79-
{"access_token":"eyJ0eXAiOi...",
80-
"refresh_token":"",
81-
"expires_in":"3599",
82-
"expires_on":"1504130527",
83-
"not_before":"1504126627",
84-
"resource":"https://management.azure.com",
85-
"token_type":"Bearer"} 
86-
```
87-
88-
You can use this access token to access Azure Resource Manager, for example to read the details of the Resource Group to which you previously granted this VM access. Replace the values of \<SUBSCRIPTION ID\>, \<RESOURCE GROUP\>, and \<ACCESS TOKEN\> with the ones you created earlier. 
89-
90-
> [!NOTE]
91-
> The URL is case-sensitive, so ensure if you are using the exact same case as you used earlier when you named the Resource Group, and the uppercase “G” in “resourceGroup”.  
92-
93-
```bash
94-
curl https://management.azure.com/subscriptions/<SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP>?api-version=2016-09-01 -H "Authorization: Bearer <ACCESS TOKEN>" 
95-
```
96-
97-
The response back with the specific Resource Group information: 
98-
 
99-
```bash
100-
{"id":"/subscriptions/98f51385-2edc-4b79-bed9-7718de4cb861/resourceGroups/DevTest","name":"DevTest","location":"westus","properties":{"provisioningState":"Succeeded"}} 
101-
```
103+
```json
104+
{
105+
"id":"/subscriptions/98f51385-2edc-4b79-bed9-7718de4cb861/resourceGroups/DevTest",
106+
"name":"DevTest",
107+
"location":"westus",
108+
"properties":
109+
{
110+
"provisioningState":"Succeeded"
111+
}
112+
} 
113+
```
102114

103115
## Next steps
104116

105-
In this quickstart, you learned how to use a system-assigned managed identity to access the Azure Resource Manager API. To learn more about Azure Resource Manager see:
117+
In this quickstart, you learned how to use a system-assigned managed identity to access the Azure Resource Manager API. For more information about Azure Resource Manager, see:
106118

107119
> [!div class="nextstepaction"]
108120
>[Azure Resource Manager](../../azure-resource-manager/management/overview.md)

‎articles/active-directory/reports-monitoring/concept-sign-ins.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Sign-in logs in Microsoft Entra ID
3-
description: Learn about the four types of sign-in logs available in Microsoft Entra Monitoring and health.
3+
description: Learn about the four types of sign-in logs available in Microsoft Entra monitoring and health.
44
services: active-directory
55
author: shlipsey3
66
manager: amycolannino

‎articles/active-directory/reports-monitoring/howto-configure-prerequisites-for-reporting-api.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ To get access to the reporting data through the API, you need to have one of the
2929

3030
In order to access the sign-in reports for a tenant, a Microsoft Entra tenant must have associated Microsoft Entra ID P1 or P2 license. If the directory type is Azure AD B2C, the sign-in reports are accessible through the API without any other license requirement.
3131

32-
Registration is needed even if you're accessing the reporting API using a script. The registration gives you an **Application ID**, which is required for the authorization calls and enables your code to receive tokens. To configure your directory to access the Microsoft Entra ID reporting API, you must sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/) in one of the required roles.
32+
Registration is needed even if you're accessing the reporting API using a script. The registration gives you an **Application ID**, which is required for the authorization calls and enables your code to receive tokens. To configure your directory to access the Microsoft Entra reporting API, you must sign in to the [Microsoft Entra admin center](https://entra.microsoft.com/) in one of the required roles.
3333

3434
> [!IMPORTANT]
3535
> Applications running under credentials with administrator privileges can be very powerful, so be sure to keep the application's ID and secret credentials in a secure location.
@@ -61,7 +61,7 @@ To enable your application to access Microsoft Graph without user intervention,
6161

6262
### Grant permissions
6363

64-
To access the Microsoft Entra ID reporting API, you must grant your app *Read directory data* and *Read all audit log data* permissions for the Microsoft Graph API.
64+
To access the Microsoft Entra reporting API, you must grant your app *Read directory data* and *Read all audit log data* permissions for the Microsoft Graph API.
6565

6666
1. Browse to **Identity** > **Applications** > **App Registrations**.
6767
1. Select **Add a permission**.
@@ -95,7 +95,7 @@ Once you have the app registration configured, you can run activity log queries
9595

9696
## Access reports using Microsoft Graph PowerShell
9797

98-
To use PowerShell to access the Microsoft Entra ID reporting API, you need to gather a few configuration settings. These settings were created as a part of the [app registration process](#register-an-azure-ad-application).
98+
To use PowerShell to access the Microsoft Entra reporting API, you need to gather a few configuration settings. These settings were created as a part of the [app registration process](#register-an-azure-ad-application).
9999

100100
- Tenant ID
101101
- Client app ID
@@ -129,7 +129,7 @@ Programmatic access APIs:
129129

130130
<a name='troubleshoot-errors-in-azure-active-directory-reporting-api'></a>
131131

132-
### Troubleshoot errors in Microsoft Entra ID reporting API
132+
### Troubleshoot errors in Microsoft Entra reporting API
133133

134134
**500 HTTP internal server error while accessing Microsoft Graph beta endpoint**: We don't currently support the Microsoft Graph beta endpoint - make sure to access the activity logs using the Microsoft Graph v1.0 endpoint.
135135
- GET `https://graph.microsoft.com/v1.0/auditLogs/directoryAudits`

‎articles/active-directory/reports-monitoring/howto-manage-inactive-user-accounts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,6 @@ The last sign-in date and time shown on this tile may take up to 6 hours to upda
8686

8787
## Next steps
8888

89-
* [Get data using the Microsoft Entra ID reporting API with certificates](./howto-configure-prerequisites-for-reporting-api.md)
89+
* [Get data using the Microsoft Entra reporting API with certificates](./howto-configure-prerequisites-for-reporting-api.md)
9090
* [Audit API reference](/graph/api/resources/directoryaudit)
9191
* [Sign-in activity report API reference](/graph/api/resources/signin)

‎articles/active-directory/reports-monitoring/howto-stream-logs-to-event-hub.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Download and open the [configuration guide for ArcSight SmartConnector for Azure
8787
1. Complete the steps in the **Prerequisites** section of the ArcSight configuration guide. This section includes the following steps:
8888
* Set user permissions in Azure to ensure there's a user with the **owner** role to deploy and configure the connector.
8989
* Open ports on the server with Syslog NG Daemon SmartConnector so it's accessible from Azure.
90-
* The deployment runs a Windows PowerShell script, so you must enable PowerShell to run scripts on the machine where you want to deploy the connector.
90+
* The deployment runs a PowerShell script, so you must enable PowerShell to run scripts on the machine where you want to deploy the connector.
9191

9292
1. Follow the steps in the **Deploying the Connector** section of the ArcSight configuration guide to deploy the connector. This section walks you through how to download and extract the connector, configure application properties and run the deployment script from the extracted folder.
9393

‎articles/active-directory/reports-monitoring/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
### YamlMime:Landing
22

3-
title: Microsoft Entra Monitoring and health documentation
3+
title: Microsoft Entra monitoring and health documentation
44
summary: Learn how to access and use logs, reports, monitoring integrations, workbooks, and recommendations in Microsoft Entra ID.
55

66
metadata:
7-
title: Microsoft Entra Monitoring and health documentation
7+
title: Microsoft Entra monitoring and health documentation
88
description: Learn how to use the logs, reports, and monitoring tools in Microsoft Entra ID.
99
services: active-directory
1010
ms.service: active-directory

0 commit comments

Comments
 (0)