Skip to content

Commit 6eb62e2

Browse files
committed
Acrolinx and validation fixes
1 parent c205820 commit 6eb62e2

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

articles/active-directory/standards/memo-22-09-authorization.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ M-22-09 specifically requires the use of at least one device-based signal when y
3030
| - | - |
3131
| Device must be managed| Integration with Intune or another mobile device management (MDM) solution that supports this integration is required.
3232
Hybrid Azure AD joined| The device is managed by Active Directory and qualifies.
33-
| Device must be compliant| Integration with Intune or another MDM solutions that supports this integration is required. For more information, see [Use device compliance policies to set rules for devices you manage with Intune](/mem/intune/protect/device-compliance-get-started). |
33+
| Device must be compliant| Integration with Intune or another MDM solution that supports this integration is required. For more information, see [Use device compliance policies to set rules for devices you manage with Intune](/mem/intune/protect/device-compliance-get-started). |
3434
| Threat signals| Microsoft Defender for Endpoint and other endpoint detection and response (EDR) tools have integrations with Azure AD and Intune to send threat signals that can be used to deny access. Threat signals are part of the compliant status signal. |
3535
| Cross-tenant access policies (public preview)| These policies permit an organization to trust device signals from devices that belong to other organizations. |
3636

@@ -50,7 +50,7 @@ You can use attributes assigned to users and stored in Azure AD to create author
5050

5151
### Attributes assigned to data
5252

53-
Azure AD allows integration of an authorization directly to the data. You can create integrate authorization in multiple ways.
53+
Azure AD allows integration of an authorization directly to the data. You can integrate authorization in multiple ways.
5454

5555
You can configure [authentication context](../conditional-access/concept-conditional-access-cloud-apps.md) within conditional access policies. This allows you to, for example, restrict which actions a user can take within an application or on specific data. These authentication contexts are then mapped within the data source itself.
5656

articles/active-directory/standards/memo-22-09-enterprise-wide-identity-management-system.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ During your inventory and scope phase, consider identifying your devices and inf
109109

110110
You can use [Azure Automation accounts](../../automation/change-tracking/manage-inventory-vms.md) to identify devices through inventory collection connected to Azure Monitor.
111111

112-
[Microsoft Defender for Endpoint](/microsoft-365/security/defender-endpoint/machines-view-overview?view=o365-worldwide) also features device inventory capabilities and discovery. This feature discovers which devices have Defender for Endpoint configured and which devices don't. Device inventory can also come from on-premises systems such as [System Center Configuration Manager](/mem/configmgr/core/clients/manage/inventory/introduction-to-hardware-inventory) or other systems that manage devices and clients.
112+
[Microsoft Defender for Endpoint](/microsoft-365/security/defender-endpoint/machines-view-overview) also features device inventory capabilities and discovery. This feature discovers which devices have Defender for Endpoint configured and which devices don't. Device inventory can also come from on-premises systems such as [System Center Configuration Manager](/mem/configmgr/core/clients/manage/inventory/introduction-to-hardware-inventory) or other systems that manage devices and clients.
113113

114114
### Integration of devices with Azure AD
115115

articles/active-directory/standards/memo-22-09-other-areas-zero-trust.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Automation is an important aspect of Zero Trust, particularly in remediation of
7676

7777
We recommend that you set up an Azure function or an Azure logic app to use a [system-assigned managed identity](../managed-identities-azure-resources/overview.md). Your logic app or function contains the steps or code necessary to automate the desired actions. You assign permissions to the managed identity to grant the service principal the necessary directory permissions to perform the required actions. Grant managed identities only the minimum rights necessary.
7878

79-
Another automation integration point is [Azure AD PowerShell](/powershell/azure/active-directory/overview?view=azureadps-2.0) modules. PowerShell is a useful automation tool for administrators and IT integrators who are performing common tasks or configurations in Azure AD. PowerShell can also be incorporated into Azure functions or Azure Automation runbooks.
79+
Another automation integration point is [Azure AD PowerShell](/powershell/azure/active-directory/overview) modules. PowerShell is a useful automation tool for administrators and IT integrators who are performing common tasks or configurations in Azure AD. PowerShell can also be incorporated into Azure functions or Azure Automation runbooks.
8080

8181
## Governance
8282

0 commit comments

Comments
 (0)