Skip to content

Commit

Permalink
Merge pull request #864 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
12/14/2023 PM Publish
  • Loading branch information
Taojunshen authored Dec 14, 2023
2 parents fd2d923 + 5d057d7 commit efe2f82
Show file tree
Hide file tree
Showing 4 changed files with 37 additions and 25 deletions.
58 changes: 34 additions & 24 deletions docs/global-secure-access/how-to-compliant-network.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: Learn how to require known compliant network locations in order to
ms.service: network-access
ms.subservice:
ms.topic: how-to
ms.date: 10/31/2023
ms.date: 12/14/2023

ms.author: joflore
author: MicrosoftGuyJFlo
Expand All @@ -14,36 +14,38 @@ ms.reviewer: mamkumar
---
# Enable compliant network check with Conditional Access

Organizations who use Conditional Access along with the Global Secure Access preview, can prevent malicious access to Microsoft apps, third-party SaaS apps, and private line-of-business (LoB) apps using multiple conditions to provide defense-in-depth. These conditions may include device compliance, location, and more to provide protection against user identity or token theft. Global Secure Access introduces the concept of a compliant network within Conditional Access and continuous access evaluation. This compliant network check ensures users connect from a verified network connectivity model for their specific tenant and are compliant with security policies enforced by administrators.
Organizations who use Conditional Access along with the Global Secure Access preview, can prevent malicious access to Microsoft apps, third-party SaaS apps, and private line-of-business (LoB) apps using multiple conditions to provide defense-in-depth. These conditions may include device compliance, location, and more to provide protection against user identity or token theft. Global Secure Access introduces the concept of a compliant network within Conditional Access and continuous access evaluation. This compliant network check ensures users connect from a verified network connectivity model for their specific tenant and are compliant with security policies enforced by administrators.

The Global Secure Access Client installed on devices or configured remote network allows administrators to secure resources behind a compliant network with advanced Conditional Access controls. This compliant network makes it easier for administrators to manage and maintain, without having to maintain a list of all of an organization's locations IP addresses. Administrators don't need to hairpin traffic through their organization's VPN egress points to ensure security.
The Global Secure Access Client installed on devices or users behind configured remote networks allows administrators to secure resources behind a compliant network with advanced Conditional Access controls. This compliant network feature makes it easier for administrators to manage and maintain, without having to maintain a list of all of an organization's locations IP addresses. Administrators don't need to hairpin traffic through their organization's VPN egress points to ensure security.

This compliant network check is specific to each tenant.
Continuous Access Evaluation (CAE) with the compliant network feature is currently supported for SharePoint Online. With CAE, you can enforce defense-in-depth with token theft replay protection.

- Using this check you can ensure that other organizations using Microsoft's Global Secure Access services can't access your resources.
- For example: Contoso can protect their services like Exchange Online and SharePoint Online behind their compliant network check to ensure only Contoso users can access these resources.
- If another organization like Fabrikam was using a compliant network check, they wouldn't pass Contoso's compliant network check.
This compliant network check is specific to each tenant.

The compliant network is different than [IPv4, IPv6, or geographic locations](/azure/active-directory/conditional-access/location-condition) you may configure in Microsoft Entra ID. No administrator upkeep is required.
- Using this check you can ensure that other organizations using Microsoft's Global Secure Access services can't access your resources.
- For example: Contoso can protect their services like Exchange Online and SharePoint Online behind their compliant network check to ensure only Contoso users can access these resources.
- If another organization like Fabrikam was using a compliant network check, they wouldn't pass Contoso's compliant network check.

The compliant network is different than [IPv4, IPv6, or geographic locations](../identity/conditional-access/location-condition.md) you may configure in Microsoft Entra ID. No administrator upkeep is required.

## Prerequisites

* Administrators who interact with **Global Secure Access preview** features must have one or more of the following role assignments depending on the tasks they're performing.
* The **Global Secure Access Administrator** role to manage the Global Secure Access preview features
* [Conditional Access Administrator](/azure/active-directory/roles/permissions-reference#conditional-access-administrator) or [Security Administrator](/azure/active-directory/roles/permissions-reference#security-administrator) to create and interact with Conditional Access policies and named locations.
* [Conditional Access Administrator](../identity/role-based-access-control/permissions-reference.md#conditional-access-administrator) or [Security Administrator](../identity/role-based-access-control/permissions-reference.md#security-administrator) to create and interact with Conditional Access policies and named locations.
* The preview requires a Microsoft Entra ID P1 license. If needed, you can [purchase licenses or get trial licenses](https://aka.ms/azureadlicense).
* To use the Microsoft 365 traffic forwarding profile, a Microsoft 365 E3 license is recommended.

### Known limitations

- Continuous access evaluation is not currently supported for compliant network check.
- Organizations can protect other Microsoft Entra integrated apps with Conditional Access policies requiring a compliant network check. During the preview, administrators must choose the individual applications from the app picker instead of choosing *All cloud apps*. **Do not choose *All cloud apps*.**
- Compliant network check is currently not supported for private access apps.

## Enable Global Secure Access signaling for Conditional Access

To enable the required setting to allow the compliant network check, an administrator must take the following steps.

1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as a [Global Secure Access Administrator](/azure/active-directory/roles/permissions-reference#global-secure-access-administrator).
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as a [Global Secure Access Administrator](../identity/role-based-access-control/permissions-reference.md#global-secure-access-administrator).
1. Browse to **Global Secure Access (Preview)** > **Global settings** > **Session management** **Adaptive access**.
1. Select the toggle to **Enable Global Secure Access signaling in Conditional Access**.
1. Browse to **Protection** > **Conditional Access** > **Named locations**.
Expand All @@ -52,38 +54,46 @@ To enable the required setting to allow the compliant network check, an administ
:::image type="content" source="media/how-to-compliant-network/toggle-enable-signaling-in-conditional-access.png" alt-text="Screenshot showing the toggle to enable signaling in Conditional Access.":::

> [!CAUTION]
> If your organization has active Conditional Access policies based on compliant network check, and you disable Global Secure Access signaling in Conditional Access, you may unintentionally block targeted end-users from being able to access the resources. If you must disable this feature, first delete any corresponding Conditional Access policies.
> If your organization has active Conditional Access policies based on compliant network check, and you disable Global Secure Access signaling in Conditional Access, you may unintentionally block targeted end-users from being able to access the resources. If you must disable this feature, first delete any corresponding Conditional Access policies.
## Protect your resources behind the compliant network

## Protect Exchange and SharePoint Online behind the compliant network
The compliant network Conditional Access policy can be used to protect your Microsoft 365 and third-party resources.

The following example shows a Conditional Access policy that requires Exchange Online and SharePoint Online to be accessed from behind a compliant network as part of the preview.
The following example shows this type of policy. In addition, you can enforce token theft replay protection using CAE for SharePoint Online.

1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Conditional Access Administrator](/azure/active-directory/roles/permissions-reference#conditional-access-administrator).
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Conditional Access Administrator](../identity/role-based-access-control/permissions-reference.md#conditional-access-administrator).
1. Browse to **Protection** > **Conditional Access**.
1. Select **Create new policy**.
1. Give your policy a name. We recommend that organizations create a meaningful standard for the names of their policies.
1. Under **Assignments**, select **Users or workload identities**.
1. Under **Include**, select **All users**.
1. Under **Exclude**, select **Users and groups** and choose your organization's [emergency access or break-glass accounts](#user-exclusions).
1. Under **Exclude**, select **Users and groups** and choose your organization's [emergency access or break-glass accounts](#user-exclusions).
1. Under **Target resources** > **Include**, and select **Select apps**.
1. Choose **Office 365 Exchange Online** and/or **Office 365 SharePoint Online**.
1. Office 365 apps are currently NOT supported, so do not select this option.
1. Choose **Office 365 Exchange Online**, and/or **Office 365 SharePoint Online**, and/or any of your third-party SaaS apps.
1. The specific *Office 365* cloud app in the app picker is currently NOT supported, so do not select this cloud app.
1. Under **Conditions** > **Location**.
1. Set **Configure** to **Yes**
1. Under **Include**, select **Any location**.
1. Under **Exclude**, select **Selected locations**
1. Select the **All Compliant Network locations** location.
1. Select **Select**.
1. Under **Access controls**:
1. Under **Access controls**:
1. **Grant**, select **Block Access**, and select **Select**.
1. Confirm your settings and set **Enable policy** to **Report-only**.
1. Select **Create** to create to enable your policy.

After administrators confirm the policy settings using [report-only mode](/azure/active-directory/conditional-access/howto-conditional-access-insights-reporting), an administrator can move the **Enable policy** toggle from **Report-only** to **On**.
> [!NOTE]
> Token theft replay protection is now available for SharePoint Online.
9. If your policy is only targeting SharePoint Online, for **Session**, select **Customize continuous access evaluation** and **Strictly enforce location policies (Preview)** and select **Select**.

:::image type="content" source="media/how-to-compliant-network/ca-policy-cae-settings.png" alt-text="Screenshot of the session control with the continuous access evaluation option highlighted.":::

10. Confirm your settings and set **Enable policy** to **On**.
11. Select the **Create** button to create to enable your policy.

### User exclusions

[!INCLUDE [active-directory-policy-exclusions](./includes/conditional-access-recommended-exclusions.md)]
[!INCLUDE [conditional-access-recommended-exclusions](includes/conditional-access-recommended-exclusions.md)]

## Try your compliant network policy

Expand All @@ -96,7 +106,7 @@ After administrators confirm the policy settings using [report-only mode](/azure

## Troubleshooting

Verify the new named location was automatically created using [Microsoft Graph](https://developer.microsoft.com/graph/graph-explorer).
Verify the new named location was automatically created using [Microsoft Graph](https://developer.microsoft.com/graph/graph-explorer).

`GET https://graph.microsoft.com/beta/identity/conditionalAccess/namedLocations`

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 2 additions & 0 deletions docs/id-governance/apps.md
Original file line number Diff line number Diff line change
Expand Up @@ -304,8 +304,10 @@ Microsoft Entra ID Governance can be integrated with many other applications, us
| SAML-based apps | ||
| [SAP Analytics Cloud](~/identity/saas-apps/sap-analytics-cloud-provisioning-tutorial.md) |||
| [SAP Cloud Platform](~/identity/saas-apps/sap-cloud-platform-identity-authentication-provisioning-tutorial.md) |||
| [SAP Fieldglass](~/identity/saas-apps/fieldglass-tutorial.md) | ||
| [SAP R/3 and ERP](~/identity/app-provisioning/on-premises-sap-connector-configure.md) || |
| [SAP HANA](~/identity/saas-apps/saphana-tutorial.md) |||
| [SAP NetWeaver](~/identity/saas-apps/sap-netweaver-tutorial.md) | ||
| [SAP SuccessFactors to Active Directory](~/identity/saas-apps/sap-successfactors-inbound-provisioning-tutorial.md) |||
| [SAP SuccessFactors to Microsoft Entra ID](~/identity/saas-apps/sap-successfactors-inbound-provisioning-cloud-only-tutorial.md) |||
| [SAP SuccessFactors Writeback](~/identity/saas-apps/sap-successfactors-writeback-tutorial.md) |||
Expand Down
2 changes: 1 addition & 1 deletion docs/id-governance/sap.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ In addition to the native provisioning integrations that allow you to manage acc

### Enable SSO

After you set up provisioning for your SAP applications, you can enable SSO for them. Microsoft Entra ID can serve as the identity provider and serve as the authentication authority for your SAP applications. [Learn how to configure Microsoft Entra ID as the corporate identity provider for your SAP applications](https://help.sap.com/docs/IDENTITY_AUTHENTICATION/6d6d63354d1242d185ab4830fc04feb1/058c7b14209f4f2d8de039da4330a1c1.html).
Along with setting up provisioning for your SAP applications, you can enable SSO for them. Microsoft Entra ID can serve as the identity provider and serve as the authentication authority for your SAP applications. Entra ID can integrate with [SAP NetWeaver using SAML or OAuth](~/identity/saas-apps/sap-netweaver-tutorial.md). For SAP SaaS and modern apps, [learn how to configure Microsoft Entra ID as the corporate identity provider for your SAP applications via SAP Cloud Identity Services](https://help.sap.com/docs/IDENTITY_AUTHENTICATION/6d6d63354d1242d185ab4830fc04feb1/058c7b14209f4f2d8de039da4330a1c1.html) and see the guides for [SAP Cloud Identity Services](~/identity/saas-apps/sap-hana-cloud-platform-identity-authentication-tutorial.md), [SAP HANA](~/identity/saas-apps/saphana-tutorial.md) and [SAP Fieldglass](~/identity/saas-apps/fieldglass-tutorial.md).

### Provision identities into modern SAP applications

Expand Down

0 comments on commit efe2f82

Please sign in to comment.