Skip to content

Commit 2044aa3

Browse files
authored
Merge pull request #193065 from MicrosoftDocs/main
Merge main to live, 4 AM
2 parents 0a3b523 + 9264521 commit 2044aa3

File tree

271 files changed

+2573
-1869
lines changed

Some content is hidden

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

271 files changed

+2573
-1869
lines changed

.openpublishing.redirection.json

Lines changed: 43 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -849,17 +849,17 @@
849849
"redirect_document_id": false
850850
},
851851
{
852-
"source_path_from_root": "/articles/frontdoor/concept-rule-set-actions.md",
852+
"source_path_from_root": "/articles/frontdoor/standard-premium/concept-rule-set-actions.md",
853853
"redirect_url": "/azure/frontdoor/front-door-rules-engine-actions",
854854
"redirect_document_id": false
855855
},
856856
{
857-
"source_path_from_root": "/articles/frontdoor/concept-rules-set.md",
857+
"source_path_from_root": "/articles/frontdoor/standard-premium/concept-rules-set.md",
858858
"redirect_url": "/azure/frontdoor/front-door-rules-engine",
859859
"redirect_document_id": false
860860
},
861861
{
862-
"source_path_from_root": "/articles/frontdoor/concept-caching.md",
862+
"source_path_from_root": "/articles/frontdoor/standard-premium/concept-caching.md",
863863
"redirect_url": "/azure/frontdoor/front-door-caching",
864864
"redirect_document_id": false
865865
},
@@ -868,11 +868,51 @@
868868
"redirect_url": "/azure/frontdoor/front-door-route-matching",
869869
"redirect_document_id": false
870870
},
871+
{
872+
"source_path_from_root": "/articles/frontdoor/front-door-backend-pool.md",
873+
"redirect_url": "/azure/frontdoor/origin",
874+
"redirect_document_id": true
875+
},
876+
{
877+
"source_path_from_root": "/articles/frontdoor/standard-premium/concept-origin.md",
878+
"redirect_url": "/azure/frontdoor/origin",
879+
"redirect_document_id": false
880+
},
881+
{
882+
"source_path_from_root": "/articles/frontdoor/concept-private-link.md",
883+
"redirect_url": "/azure/frontdoor/private-link",
884+
"redirect_document_id": true
885+
},
886+
{
887+
"source_path_from_root": "/articles/frontdoor/concept-end-to-end-tls.md",
888+
"redirect_url": "/azure/frontdoor/end-to-end-tls",
889+
"redirect_document_id": true
890+
},
891+
{
892+
"source_path_from_root": "/articles/frontdoor/front-door-routing-methods.md",
893+
"redirect_url": "/azure/frontdoor/routing-methods",
894+
"redirect_document_id": true
895+
},
896+
{
897+
"source_path_from_root": "/articles/frontdoor/front-door-health-probes.md",
898+
"redirect_url": "/azure/frontdoor/health-probes",
899+
"redirect_document_id": true
900+
},
901+
{
902+
"source_path_from_root": "/articles/frontdoor/standard-premium/create-front-door-portal.md",
903+
"redirect_url": "/azure/frontdoor/create-front-door-portal",
904+
"redirect_document_id": true
905+
},
871906
{
872907
"source_path_from_root": "/articles/frontdoor/concept-rule-set-url-redirect-and-rewrite.md",
873908
"redirect_url": "/azure/frontdoor/front-door-url-redirect",
874909
"redirect_document_id": false
875910
},
911+
{
912+
"source_path_from_root": "/articles/frontdoor/standard-premium/index.yml",
913+
"redirect_url": "/azure/frontdoor/",
914+
"redirect_document_id": false
915+
},
876916
{
877917
"source_path_from_root": "/articles/app-service-web/web-sites-dotnet-deploy-aspnet-mvc-app-membership-oauth-sql-database.md",
878918
"redirect_url": "/aspnet/core/security/authorization/secure-data",

articles/active-directory-b2c/custom-domain.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ The following diagram illustrates Azure Front Door integration:
4747
4848
When using custom domains, consider the following:
4949

50-
- You can set up multiple custom domains. For the maximum number of supported custom domains, see [Azure AD service limits and restrictions](../active-directory/enterprise-users/directory-service-limits-restrictions.md) for Azure AD B2C and [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-front-door-service-limits) for Azure Front Door.
50+
- You can set up multiple custom domains. For the maximum number of supported custom domains, see [Azure AD service limits and restrictions](../active-directory/enterprise-users/directory-service-limits-restrictions.md) for Azure AD B2C and [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-front-door-classic-limits) for Azure Front Door.
5151
- Azure Front Door is a separate Azure service, so extra charges will be incurred. For more information, see [Front Door pricing](https://azure.microsoft.com/pricing/details/frontdoor).
5252
- To use Azure Front Door [Web Application Firewall](../web-application-firewall/afds/afds-overview.md), you need to confirm your firewall configuration and rules work correctly with your Azure AD B2C user flows.
5353
- After you configure custom domains, users will still be able to access the Azure AD B2C default domain name *<tenant-name>.b2clogin.com* (unless you're using a custom policy and you [block access](#block-access-to-the-default-domain-name).

articles/active-directory-b2c/user-profile-attributes.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,6 @@ The table below lists the [user resource type](/graph/api/resources/user) attrib
5555
|immutableId |String|An identifier that is typically used for users migrated from on-premises Active Directory.|No|No|Persisted, Output|
5656
|legalAgeGroupClassification|String|Legal age group classification. Read-only and calculated based on ageGroup and consentProvidedForMinor properties. Allowed values: null, minorWithOutParentalConsent, minorWithParentalConsent, minorNoParentalConsentRequired, notAdult, and adult.|Yes|No|Persisted, Output|
5757
|legalCountry<sup>1</sup> |String|Country/Region for legal purposes.|No|No|Persisted, Output|
58-
|mail |String|Email address for the user. Example: "[email protected]". NOTE: Accent characters are not allowed.|Yes|No|Persisted, Output|
5958
|mailNickName |String|The mail alias for the user. Max length 64.|No|No|Persisted, Output|
6059
|mobile (mobilePhone) |String|The primary cellular telephone number for the user. Max length 64.|Yes|No|Persisted, Output|
6160
|netId |String|Net ID.|No|No|Persisted, Output|
Lines changed: 38 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with FortiSASE SIA | Microsoft Docs'
3-
description: Learn how to configure single sign-on between Azure Active Directory and FortiSASE SIA.
2+
title: 'Tutorial: Azure AD SSO integration with FortiSASE'
3+
description: Learn how to configure single sign-on between Azure Active Directory and FortiSASE.
44
services: active-directory
55
author: jeevansd
66
manager: CelesteDG
@@ -9,71 +9,71 @@ ms.service: active-directory
99
ms.subservice: saas-app-tutorial
1010
ms.workload: identity
1111
ms.topic: tutorial
12-
ms.date: 02/19/2021
12+
ms.date: 03/25/2022
1313
ms.author: jeedes
1414

1515
---
1616

17-
# Tutorial: Azure Active Directory single sign-on (SSO) integration with FortiSASE SIA
17+
# Tutorial: Azure AD SSO integration with FortiSASE
1818

19-
In this tutorial, you'll learn how to integrate FortiSASE SIA with Azure Active Directory (Azure AD). When you integrate FortiSASE SIA with Azure AD, you can:
19+
In this tutorial, you'll learn how to integrate FortiSASE with Azure Active Directory (Azure AD). When you integrate FortiSASE with Azure AD, you can:
2020

21-
* Control in Azure AD who has access to FortiSASE SIA.
22-
* Enable your users to be automatically signed-in to FortiSASE SIA with their Azure AD accounts.
21+
* Control in Azure AD who has access to FortiSASE.
22+
* Enable your users to be automatically signed-in to FortiSASE with their Azure AD accounts.
2323
* Manage your accounts in one central location - the Azure portal.
2424

2525
## Prerequisites
2626

2727
To get started, you need the following items:
2828

2929
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
30-
* FortiSASE SIA single sign-on (SSO) enabled subscription.
30+
* FortiSASE single sign-on (SSO) enabled subscription.
31+
* Along with Cloud Application Administrator, Application Administrator can also add or manage applications in Azure AD.
32+
For more information, see [Azure built-in roles](../roles/permissions-reference.md).
3133

3234
## Scenario description
3335

3436
In this tutorial, you configure and test Azure AD SSO in a test environment.
3537

36-
* FortiSASE SIA supports **SP** initiated SSO
38+
* FortiSASE supports **SP** initiated SSO.
3739

38-
* FortiSASE SIA supports **Just In Time** user provisioning
40+
* FortiSASE supports **Just In Time** user provisioning.
3941

42+
## Add FortiSASE from the gallery
4043

41-
## Adding FortiSASE SIA from the gallery
42-
43-
To configure the integration of FortiSASE SIA into Azure AD, you need to add FortiSASE SIA from the gallery to your list of managed SaaS apps.
44+
To configure the integration of FortiSASE into Azure AD, you need to add FortiSASE from the gallery to your list of managed SaaS apps.
4445

4546
1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
4647
1. On the left navigation pane, select the **Azure Active Directory** service.
4748
1. Navigate to **Enterprise Applications** and then select **All Applications**.
4849
1. To add new application, select **New application**.
49-
1. In the **Add from the gallery** section, type **FortiSASE SIA** in the search box.
50-
1. Select **FortiSASE SIA** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
51-
50+
1. In the **Add from the gallery** section, type **FortiSASE** in the search box.
51+
1. Select **FortiSASE** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
5252

53-
## Configure and test Azure AD SSO for FortiSASE SIA
53+
## Configure and test Azure AD SSO for FortiSASE
5454

55-
Configure and test Azure AD SSO with FortiSASE SIA using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in FortiSASE SIA.
55+
Configure and test Azure AD SSO with FortiSASE using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in FortiSASE.
5656

57-
To configure and test Azure AD SSO with FortiSASE SIA, perform the following steps:
57+
To configure and test Azure AD SSO with FortiSASE, perform the following steps:
5858

5959
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
6060
1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
6161
1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
62-
1. **[Configure FortiSASE SIA SSO](#configure-fortisase-sia-sso)** - to configure the single sign-on settings on application side.
63-
1. **[Create FortiSASE SIA test user](#create-fortisase-sia-test-user)** - to have a counterpart of B.Simon in FortiSASE SIA that is linked to the Azure AD representation of user.
62+
1. **[Configure FortiSASE SSO](#configure-fortisase-sso)** - to configure the single sign-on settings on application side.
63+
1. **[Create FortiSASE test user](#create-fortisase-test-user)** - to have a counterpart of B.Simon in FortiSASE that is linked to the Azure AD representation of user.
6464
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
6565

6666
## Configure Azure AD SSO
6767

6868
Follow these steps to enable Azure AD SSO in the Azure portal.
6969

70-
1. In the Azure portal, on the **FortiSASE SIA** application integration page, find the **Manage** section and select **single sign-on**.
70+
1. In the Azure portal, on the **FortiSASE** application integration page, find the **Manage** section and select **single sign-on**.
7171
1. On the **Select a single sign-on method** page, select **SAML**.
7272
1. On the **Set up single sign-on with SAML** page, click the pencil icon for **Basic SAML Configuration** to edit the settings.
7373

7474
![Edit Basic SAML Configuration](common/edit-urls.png)
7575

76-
1. On the **Basic SAML Configuration** section, enter the values for the following fields:
76+
1. On the **Basic SAML Configuration** section, perform the following steps:
7777

7878
a. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
7979
`https://<TENANTHOSTNAME>.edge.prod.fortisase.com/remote/saml/metadata`
@@ -85,13 +85,13 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
8585
`https://<TENANTHOSTNAME>.edge.prod.fortisase.com/remote/login`
8686

8787
> [!NOTE]
88-
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [FortiSASE SIA Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
88+
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign on URL. Contact [FortiSASE Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
8989

90-
1. FortiSASE SIA application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
90+
1. FortiSASE application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
9191

9292
![image](common/default-attributes.png)
9393

94-
1. In addition to above, FortiSASE SIA application expects few more attributes to be passed back in SAML response, which are shown below. These attributes are also pre populated but you can review them as per your requirements.
94+
1. In addition to above, FortiSASE application expects few more attributes to be passed back in SAML response, which are shown below. These attributes are also pre populated but you can review them as per your requirements.
9595

9696
| Name | Source Attribute|
9797
| --------------- | --------- |
@@ -102,9 +102,10 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
102102

103103
![The Certificate download link](common/certificatebase64.png)
104104

105-
1. On the **Set up FortiSASE SIA** section, copy the appropriate URL(s) based on your requirement.
105+
1. On the **Set up FortiSASE** section, copy the appropriate URL(s) based on your requirement.
106106

107107
![Copy configuration URLs](common/copy-configuration-urls.png)
108+
108109
### Create an Azure AD test user
109110

110111
In this section, you'll create a test user in the Azure portal called B.Simon.
@@ -119,34 +120,34 @@ In this section, you'll create a test user in the Azure portal called B.Simon.
119120

120121
### Assign the Azure AD test user
121122

122-
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to FortiSASE SIA.
123+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to FortiSASE.
123124

124125
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
125-
1. In the applications list, select **FortiSASE SIA**.
126+
1. In the applications list, select **FortiSASE**.
126127
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
127128
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
128129
1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
129130
1. If you are expecting a role to be assigned to the users, you can select it from the **Select a role** dropdown. If no role has been set up for this app, you see "Default Access" role selected.
130131
1. In the **Add Assignment** dialog, click the **Assign** button.
131132

132-
## Configure FortiSASE SIA SSO
133+
## Configure FortiSASE SSO
133134

134-
To configure single sign-on on **FortiSASE SIA** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [FortiSASE SIA support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
135+
To configure single sign-on on **FortiSASE** side, you need to send the downloaded **Certificate (Base64)** and appropriate copied URLs from Azure portal to [FortiSASE support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
135136

136-
### Create FortiSASE SIA test user
137+
### Create FortiSASE test user
137138

138-
In this section, a user called Britta Simon is created in FortiSASE SIA. FortiSASE SIA supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in FortiSASE SIA, a new one is created after authentication.
139+
In this section, a user called Britta Simon is created in FortiSASE. FortiSASE supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in FortiSASE, a new one is created after authentication.
139140

140141
## Test SSO
141142

142143
In this section, you test your Azure AD single sign-on configuration with following options.
143144

144-
* Click on **Test this application** in Azure portal. This will redirect to FortiSASE SIA Sign-on URL where you can initiate the login flow.
145+
* Click on **Test this application** in Azure portal. This will redirect to FortiSASE Sign-on URL where you can initiate the login flow.
145146

146-
* Go to FortiSASE SIA Sign-on URL directly and initiate the login flow from there.
147+
* Go to FortiSASE Sign-on URL directly and initiate the login flow from there.
147148

148-
* You can use Microsoft My Apps. When you click the FortiSASE SIA tile in the My Apps, this will redirect to FortiSASE SIA Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](https://support.microsoft.com/account-billing/sign-in-and-start-apps-from-the-my-apps-portal-2f3b1bae-0e5a-4a86-a33e-876fbd2a4510).
149+
* You can use Microsoft My Apps. When you click the FortiSASE tile in the My Apps, this will redirect to FortiSASE Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](https://support.microsoft.com/account-billing/sign-in-and-start-apps-from-the-my-apps-portal-2f3b1bae-0e5a-4a86-a33e-876fbd2a4510).
149150

150151
## Next steps
151152

152-
Once you configure FortiSASE SIA you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app).
153+
Once you configure FortiSASE you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Defender for Cloud Apps](/cloud-app-security/proxy-deployment-any-app).

0 commit comments

Comments
 (0)