Skip to content

Commit e61b8d4

Browse files
authored
Merge pull request #252775 from alexbuckgit/alexbuckgit/docutune-autopr-20230925-215651-9171852-ignore-build
[BULK] - DocuTune - Cleanup pass for Microsoft Entra rebrand (part 2)
2 parents 3a5cee2 + 967b29b commit e61b8d4

30 files changed

+150
-149
lines changed

articles/active-directory/architecture/4-secure-access-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Determine who is granted permissions to create groups: Administrators, employees
4949
* Internal and external users can join groups in your tenant
5050
* Users can create Microsoft 365 Groups
5151
* [Manage who can create Microsoft 365 Groups](/microsoft-365/solutions/manage-creation-of-groups?view=o365-worldwide&preserve-view=true)
52-
* Use Windows PowerShell to configure this setting
52+
* Use PowerShell to configure this setting
5353
* [Restrict your Microsoft Entra app to a set of users in a Microsoft Entra tenant](../develop/howto-restrict-your-app-to-a-set-of-users.md)
5454
* [Set up self-service group management in Microsoft Entra ID](../enterprise-users/groups-self-service-management.md)
5555
* [Troubleshoot and resolve groups issues](../enterprise-users/groups-troubleshooting.md)

articles/active-directory/architecture/9-secure-access-teams-sharepoint.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Sharing in Microsoft 365 is partially governed by the **External Identities, Ext
3434
Learn more:
3535

3636
* [Microsoft Entra admin center](https://entra.microsoft.com)
37-
* [External Identities in Azure AD](../external-identities/external-identities-overview.md)
37+
* [External Identities in Microsoft Entra ID](../external-identities/external-identities-overview.md)
3838

3939
### Guest user access
4040

articles/active-directory/architecture/monitor-sign-in-health-for-resilience.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ During an impacting event, two things may happen:
3737
- A Microsoft Entra tenant.
3838
- A user with global administrator or security administrator role for the Microsoft Entra tenant.
3939
- A Log Analytics workspace in your Azure subscription to send logs to Azure Monitor logs. Learn how to [create a Log Analytics workspace](../../azure-monitor/logs/quick-create-workspace.md).
40-
- Microsoft Entra ID logs integrated with Azure Monitor logs. Learn how to [Integrate Microsoft Entra Sign- in Logs with Azure Monitor Stream.](../reports-monitoring/howto-integrate-activity-logs-with-log-analytics.md)
40+
- Microsoft Entra ID logs integrated with Azure Monitor logs. Learn how to [Integrate Microsoft Entra sign-in logs with Azure Monitor Stream.](../reports-monitoring/howto-integrate-activity-logs-with-log-analytics.md)
4141

4242
## Configure the App sign-in health workbook
4343

articles/active-directory/architecture/ops-guide-auth.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -358,15 +358,15 @@ If available, use a security information and event management (SIEM) solution t
358358

359359
<a name='azure-ad-logs-archived-and-integrated-with-incident-response-plans'></a>
360360

361-
### Microsoft Entra ID logs archived and integrated with incident response plans
361+
### Microsoft Entra logs archived and integrated with incident response plans
362362

363-
Having access to sign-in activity, audits and risk events for Microsoft Entra ID is crucial for troubleshooting, usage analytics, and forensics investigations. Microsoft Entra ID provides access to these sources through REST APIs that have a limited retention period. A security information and event management (SIEM) system, or equivalent archival technology, is key for long-term storage of audits and supportability. To enable long-term storage of Microsoft Entra ID Logs, you must either add them to your existing SIEM solution or use [Azure Monitor](../reports-monitoring/concept-activity-logs-azure-monitor.md). Archive logs that can be used as part of your incident response plans and investigations.
363+
Having access to sign-in activity, audits and risk events for Microsoft Entra ID is crucial for troubleshooting, usage analytics, and forensics investigations. Microsoft Entra ID provides access to these sources through REST APIs that have a limited retention period. A security information and event management (SIEM) system, or equivalent archival technology, is key for long-term storage of audits and supportability. To enable long-term storage of Microsoft Entra logs, you must either add them to your existing SIEM solution or use [Azure Monitor](../reports-monitoring/concept-activity-logs-azure-monitor.md). Archive logs that can be used as part of your incident response plans and investigations.
364364

365365
#### Logs recommended reading
366366

367367
- [Microsoft Entra ID audit API reference](/graph/api/resources/directoryaudit)
368368
- [Microsoft Entra sign-in activity report API reference](/graph/api/resources/signin)
369-
- [Get data using the Microsoft Entra ID Reporting API with certificates](../reports-monitoring/howto-configure-prerequisites-for-reporting-api.md)
369+
- [Get data using the Microsoft Entra reporting API with certificates](../reports-monitoring/howto-configure-prerequisites-for-reporting-api.md)
370370
- [Microsoft Graph for Microsoft Entra ID Protection](../identity-protection/howto-identity-protection-graph-api.md)
371371
- [Office 365 Management Activity API reference](/office/office-365-management-api/office-365-management-activity-api-reference)
372372
- [How to use the Microsoft Entra ID Power BI Content Pack](../reports-monitoring/howto-use-azure-monitor-workbooks.md)
@@ -386,7 +386,7 @@ There are 12 aspects to a secure Identity infrastructure. This list will help yo
386386
- Lock down legacy authentication protocols.
387387
- Detect and remediate illicit consent grants.
388388
- Lock down user and group settings.
389-
- Enable long-term storage of Microsoft Entra ID logs for troubleshooting, usage analytics, and forensics investigations.
389+
- Enable long-term storage of Microsoft Entra logs for troubleshooting, usage analytics, and forensics investigations.
390390

391391
## Next steps
392392

articles/active-directory/architecture/protect-m365-from-on-premises-attacks.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ Deploy Microsoft Entra joined Windows 10 workstations with mobile device managem
178178

179179
- **Application and workload servers**
180180

181-
Applications or resources that required servers can be migrated to Azure infrastructure as a service (IaaS). Use Microsoft Entra Domain Services (Microsoft Entra DS) to decouple trust and dependency on on-premises instances of Active Directory. To achieve this decoupling, make sure virtual networks used for Microsoft Entra DS don't have a connection to corporate networks. See [Microsoft Entra Domain Services](../../active-directory-domain-services/overview.md).
181+
Applications or resources that required servers can be migrated to Azure infrastructure as a service (IaaS). Use Microsoft Entra Domain Services to decouple trust and dependency on on-premises instances of Active Directory. To achieve this decoupling, make sure virtual networks used for Microsoft Entra Domain Services don't have a connection to corporate networks. See [Microsoft Entra Domain Services](../../active-directory-domain-services/overview.md).
182182

183183
Use credential tiering. Application servers are typically considered tier-1 assets. For more information, see [Enterprise access model](/security/compass/privileged-access-access-model#ADATM_BM).
184184

@@ -198,7 +198,7 @@ Use Microsoft Entra Conditional Access to interpret signals and use them to make
198198

199199
## Monitor
200200

201-
After you configure your environment to protect your Microsoft 365 from an on-premises compromise, proactively monitor the environment. For more information, see [What is Microsoft Entra ID monitoring](../reports-monitoring/overview-monitoring.md).
201+
After you configure your environment to protect your Microsoft 365 from an on-premises compromise, proactively monitor the environment. For more information, see [What is Microsoft Entra monitoring?](../reports-monitoring/overview-monitoring-health.md)
202202

203203
### Scenarios to monitor
204204

@@ -253,9 +253,9 @@ Monitor the following key scenarios, in addition to any scenarios specific to yo
253253

254254
Define a log storage and retention strategy, design, and implementation to facilitate a consistent tool set. For example, you could consider security information and event management (SIEM) systems like Microsoft Sentinel, common queries, and investigation and forensics playbooks.
255255

256-
- **Microsoft Entra ID logs**. Ingest generated logs and signals by consistently following best practices for settings such as diagnostics, log retention, and SIEM ingestion.
256+
- **Microsoft Entra logs**. Ingest generated logs and signals by consistently following best practices for settings such as diagnostics, log retention, and SIEM ingestion.
257257

258-
The log strategy must include the following Microsoft Entra ID logs:
258+
The log strategy must include the following Microsoft Entra logs:
259259

260260
- Sign-in activity
261261
- Audit logs
@@ -265,7 +265,7 @@ Define a log storage and retention strategy, design, and implementation to facil
265265

266266
Use the Microsoft Graph API to ingest risk events. See [Use the Microsoft Graph identity protection APIs](/graph/api/resources/identityprotection-root).
267267

268-
You can stream Microsoft Entra ID logs to Azure Monitor logs. See [Integrate Microsoft Entra ID logs with Azure Monitor logs](../reports-monitoring/howto-integrate-activity-logs-with-log-analytics.md).
268+
You can stream Microsoft Entra logs to Azure Monitor logs. See [Integrate Microsoft Entra logs with Azure Monitor logs](../reports-monitoring/howto-integrate-activity-logs-with-log-analytics.md).
269269

270270
- **Hybrid infrastructure operating system security logs**. All hybrid identity infrastructure operating system logs should be archived and carefully monitored as a tier-0 system, because of the surface-area implications. Include the following elements:
271271

articles/active-directory/architecture/resilience-client-app.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -87,14 +87,14 @@ We recommend developers build a process to use the latest MSAL release because a
8787

8888
Find the latest version and release notes:
8989

90-
* [microsoft-authentication-library-for--js](https://github.com/AzureAD/microsoft-authentication-library-for-js/releases)
91-
* [microsoft-authentication-library-for--dotnet](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/releases)
92-
* [microsoft-authentication-library-for--python](https://github.com/AzureAD/microsoft-authentication-library-for-python/releases)
93-
* [microsoft-authentication-library-for--java](https://github.com/AzureAD/microsoft-authentication-library-for-java/releases)
94-
* [microsoft-authentication-library-for--objc](https://github.com/AzureAD/microsoft-authentication-library-for-objc/releases)
95-
* [microsoft-authentication-library-for--android](https://github.com/AzureAD/microsoft-authentication-library-for-android/releases)
96-
* [microsoft-authentication-library-for--js](https://github.com/AzureAD/microsoft-authentication-library-for-js/releases)
97-
* [microsoft-identity-web](https://github.com/AzureAD/microsoft-identity-web/releases)
90+
* [`microsoft-authentication-library-for-js`](https://github.com/AzureAD/microsoft-authentication-library-for-js/releases)
91+
* [`microsoft-authentication-library-for-dotnet`](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/releases)
92+
* [`microsoft-authentication-library-for-python`](https://github.com/AzureAD/microsoft-authentication-library-for-python/releases)
93+
* [`microsoft-authentication-library-for-java`](https://github.com/AzureAD/microsoft-authentication-library-for-java/releases)
94+
* [`microsoft-authentication-library-for-objc`](https://github.com/AzureAD/microsoft-authentication-library-for-objc/releases)
95+
* [`microsoft-authentication-library-for-android`](https://github.com/AzureAD/microsoft-authentication-library-for-android/releases)
96+
* [`microsoft-authentication-library-for-js`](https://github.com/AzureAD/microsoft-authentication-library-for-js/releases)
97+
* [`microsoft-identity-web`](https://github.com/AzureAD/microsoft-identity-web/releases)
9898

9999
## Resilient patterns for token handling
100100

@@ -216,7 +216,7 @@ Learn more:
216216
* [Conditional Access policy evaluation](../conditional-access/concept-continuous-access-evaluation.md#conditional-access-policy-evaluation)
217217
* [How to use CAE enabled APIs in your applications](../develop/app-resilience-continuous-access-evaluation.md)
218218

219-
If you develop resource APIs, go to openid.net for [Shared Signals – A Secure Webhooks Framework](https://openid.net/wg/sse/).
219+
If you develop resource APIs, go to `openid.net` for [Shared Signals – A Secure Webhooks Framework](https://openid.net/wg/sse/).
220220

221221
## Next steps
222222

articles/active-directory/architecture/secure-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -349,7 +349,7 @@ Detailed information on using automated or manual processes and tools to monitor
349349

350350
Some environments might have regulatory requirements that limit which data (if any) can leave a given environment. If centralized monitoring across environments isn't possible, teams should have operational procedures to correlate activities of identities across environments for auditing and forensics purposes such as cross-environment lateral movement attempts. It's recommended that the object unique identifiers human identities belonging to the same person is discoverable, potentially as part of the identity provisioning systems.
351351

352-
The log strategy must include the following Microsoft Entra ID logs for each tenant used in the organization:
352+
The log strategy must include the following Microsoft Entra logs for each tenant used in the organization:
353353

354354
* Sign-in activity
355355

0 commit comments

Comments
 (0)