Skip to content

Commit 01e2edb

Browse files
authored
Merge pull request #207354 from MicrosoftDocs/main
Merge main to live, 4 AM
2 parents 733d131 + a4db344 commit 01e2edb

File tree

136 files changed

+2760
-1340
lines changed

Some content is hidden

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

136 files changed

+2760
-1340
lines changed

articles/active-directory/fundamentals/active-directory-data-storage-japan.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010
ms.subservice: fundamentals
1111
ms.workload: identity
1212
ms.topic: conceptual
13-
ms.date: 04/12/2022
13+
ms.date: 08/08/2022
1414
ms.custom: "it-pro, seodec18, references_regions"
1515
ms.collection: M365-identity-device-management
1616
---
@@ -21,9 +21,7 @@ Azure Active Directory (Azure AD) stores its Customer Data in a geographical loc
2121

2222
For information about where Azure AD and other Microsoft services' data is located, see the [Where your data is located](https://www.microsoft.com/trust-center/privacy/data-location) section of the Microsoft Trust Center.
2323

24-
From April 15, 2022, Microsoft began storing Azure AD’s Customer Data for new tenants with a Japan billing address within the Japanese datacenters. From April 15, 2022 to June 30, 2022 a backup copy of the Azure AD’s Customer Data for these new tenants will be stored in Asia to ensure a smooth transition to the Japanese datacenters. This copy will be destroyed on June 30, 2022.
25-
26-
Additionally, certain Azure AD features do not yet support storage of Customer Data in Japan. Please go to the [Azure AD data map](https://msit.powerbi.com/view?r=eyJrIjoiYzEyZTc5OTgtNTdlZS00ZTVkLWExN2ItOTM0OWU4NjljOGVjIiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9), for specific feature information. For example, Microsoft Azure AD Multi-Factor Authentication stores Customer Data in the US and processes it globally. See [Data residency and customer data for Azure AD Multi-Factor Authentication](../authentication/concept-mfa-data-residency.md).
24+
Additionally, certain Azure AD features do not yet support storage of Customer Data in Japan. Please go to the [Azure AD data map](https://aka.ms/aaddatamap), for specific feature information. For example, Microsoft Azure AD Multi-Factor Authentication stores Customer Data in the US and processes it globally. See [Data residency and customer data for Azure AD Multi-Factor Authentication](../authentication/concept-mfa-data-residency.md).
2725

2826
> [!NOTE]
2927
> Microsoft products, services, and third-party applications that integrate with Azure AD have access to Customer Data. Evaluate each product, service, and application you use to determine how Customer Data is processed by that specific product, service, and application, and whether they meet your company's data storage requirements. For more information about Microsoft services' data residency, see the [Where your data is located](https://www.microsoft.com/trust-center/privacy/data-location) section of the Microsoft Trust Center.

articles/active-directory/roles/permissions-reference.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,7 @@ This article lists the Azure AD built-in roles you can assign to allow managemen
110110
> | [Virtual Visits Administrator](#virtual-visits-administrator) | Manage and share Virtual Visits information and metrics from admin centers or the Virtual Visits app. | e300d9e7-4a2b-4295-9eff-f1c78b36cc98 |
111111
> | [Windows 365 Administrator](#windows-365-administrator) | Can provision and manage all aspects of Cloud PCs. | 11451d60-acb2-45eb-a7d6-43d0f0125c13 |
112112
> | [Windows Update Deployment Administrator](#windows-update-deployment-administrator) | Can create and manage all aspects of Windows Update deployments through the Windows Update for Business deployment service. | 32696413-001a-46ae-978c-ce0f6b3620d2 |
113+
> | [Yammer Administrator](#yammer-administrator) | Manage all aspects of the Yammer service. | 810a2642-a034-447f-a5e8-41beaa378541 |
113114
114115
## Application Administrator
115116

@@ -2311,6 +2312,38 @@ Users in this role can create and manage all aspects of Windows Update deploymen
23112312
> | --- | --- |
23122313
> | microsoft.windows.updatesDeployments/allEntities/allProperties/allTasks | Read and configure all aspects of Windows Update Service |
23132314
2315+
## Yammer Administrator
2316+
2317+
Assign the Yammer Administrator role to users who need to do the following tasks:
2318+
2319+
- Manage all aspects of Yammer
2320+
- Create, manage, and restore Microsoft 365 Groups, but not role-assignable groups
2321+
- View the hidden members of Security groups and Microsoft 365 groups, including role assignable groups
2322+
- Read usage reports in the Microsoft 365 admin center
2323+
- Create and manage service requests in the Microsoft 365 admin center
2324+
- View announcements in the Message center, but not security announcements
2325+
- View service health
2326+
2327+
[Learn more](/yammer/manage-yammer-users/manage-yammer-admins)
2328+
2329+
> [!div class="mx-tableFixed"]
2330+
> | Actions | Description |
2331+
> | --- | --- |
2332+
> | microsoft.directory/groups/hiddenMembers/read | Read hidden members of Security groups and Microsoft 365 groups, including role-assignable groups |
2333+
> | microsoft.directory/groups.unified/create | Create Microsoft 365 groups, excluding role-assignable groups |
2334+
> | microsoft.directory/groups.unified/delete | Delete Microsoft 365 groups, excluding role-assignable groups |
2335+
> | microsoft.directory/groups.unified/restore | Restore Microsoft 365 groups from soft-deleted container, excluding role-assignable groups |
2336+
> | microsoft.directory/groups.unified/basic/update | Update basic properties on Microsoft 365 groups, excluding role-assignable groups |
2337+
> | microsoft.directory/groups.unified/members/update | Update members of Microsoft 365 groups, excluding role-assignable groups |
2338+
> | microsoft.directory/groups.unified/owners/update | Update owners of Microsoft 365 groups, excluding role-assignable groups |
2339+
> | microsoft.office365.messageCenter/messages/read | Read messages in Message Center in the Microsoft 365 admin center, excluding security messages |
2340+
> | microsoft.office365.network/performance/allProperties/read | Read all network performance properties in the Microsoft 365 admin center |
2341+
> | microsoft.office365.serviceHealth/allEntities/allTasks | Read and configure Service Health in the Microsoft 365 admin center |
2342+
> | microsoft.office365.supportTickets/allEntities/allTasks | Create and manage Microsoft 365 service requests |
2343+
> | microsoft.office365.usageReports/allEntities/allProperties/read | Read Office 365 usage reports |
2344+
> | microsoft.office365.webPortal/allEntities/standard/read | Read basic properties on all resources in the Microsoft 365 admin center |
2345+
> | microsoft.office365.yammer/allEntities/allProperties/allTasks | Manage all aspects of Yammer |
2346+
23142347
## How to understand role permissions
23152348

23162349
The schema for permissions loosely follows the REST format of Microsoft Graph:

articles/active-directory/saas-apps/crowdstrike-falcon-platform-tutorial.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: saas-app-tutorial
1010
ms.workload: identity
1111
ms.topic: tutorial
12-
ms.date: 06/28/2022
12+
ms.date: 07/29/2022
1313
ms.author: jeedes
1414

1515
---
@@ -105,10 +105,10 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
105105

106106
| Sign-on URL |
107107
| -------------- |
108-
| `https://falcon.crowdstrike.com/login` |
109-
| `https://falcon.us-2.crowdstrike.com/login` |
110-
| `https://falcon.eu-1.crowdstrike.com/login` |
111-
| `https://falcon.laggar.gcw.crowdstrike.com/login` |
108+
| `https://falcon.crowdstrike.com/login/sso` |
109+
| `https://falcon.us-2.crowdstrike.com/login/sso` |
110+
| `https://falcon.eu-1.crowdstrike.com/login/sso` |
111+
| `https://falcon.laggar.gcw.crowdstrike.com/login/sso` |
112112
|
113113

114114
1. On the **Set up single sign-on with SAML** page, In the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
59 KB
Loading
69.8 KB
Loading
35 KB
Loading
74.9 KB
Loading
30.4 KB
Loading
-27.9 KB
Loading

articles/active-directory/saas-apps/mist-cloud-admin-tutorial.md

Lines changed: 54 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: saas-app-tutorial
1010
ms.workload: identity
1111
ms.topic: tutorial
12-
ms.date: 07/28/2022
12+
ms.date: 08/02/2022
1313
ms.author: jeedes
1414

1515
---
@@ -18,16 +18,16 @@ ms.author: jeedes
1818

1919
In this tutorial, you'll learn how to integrate Mist Cloud Admin SSO with Azure Active Directory (Azure AD). When you integrate Mist Cloud Admin SSO with Azure AD, you can:
2020

21-
* Control in Azure AD who has access to Mist Cloud Admin SSO.
22-
* Enable your users to be automatically signed-in to Mist Cloud Admin SSO with their Azure AD accounts.
21+
* Control in Azure AD who has access to the Mist dashboard.
22+
* Enable your users to be automatically signed-in to the Mist dashboard 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-
* Mist Cloud Admin SSO single sign-on (SSO) enabled subscription.
30+
* Mist Cloud account, you can create an account [here](https://manage.mist.com/).
3131
* Along with Cloud Application Administrator, Application Administrator can also add or manage applications in Azure AD.
3232
For more information, see [Azure built-in roles](../roles/permissions-reference.md).
3333

@@ -50,17 +50,36 @@ To configure the integration of Mist Cloud Admin SSO into Azure AD, you need to
5050

5151
## Configure and test Azure AD SSO for Mist Cloud Admin SSO
5252

53-
Configure and test Azure AD SSO with Mist Cloud Admin SSO 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 at Mist Cloud Admin SSO.
53+
Configure and test Azure AD SSO with Mist Cloud Admin SSO using a test user called **B.Simon**. For SSO to work, you need to establish a link between your Azure AD app and Mist organization SSO.
5454

5555
To configure and test Azure AD SSO with Mist Cloud Admin SSO, perform the following steps:
5656

57+
1. **[Perform initial configuration of the Mist Cloud SSO](#perform-initial-configuration-of-the-mist-cloud-sso)** - to generate ACS URL on the application side.
5758
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
59+
1. **[Create Role for the SSO Application](#create-role-for-the-sso-application)**
5860
1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
5961
1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
60-
1. **[Configure Mist Cloud Admin SSO](#configure-mist-cloud-admin-sso)** - to configure the single sign-on settings on application side.
61-
1. **[Create Mist Cloud Admin SSO test user](#create-mist-cloud-admin-sso-test-user)** - to have a counterpart of B.Simon in Mist Cloud Admin SSO that is linked to the Azure AD representation of user.
62+
63+
1. **[Complete configuration of the Mist Cloud](#complete-configuration-of-the-mist-cloud)**
64+
65+
1. **[Create Roles to link roles sent by the Azure AD](#create-roles-to-link-roles-sent-by-the-azure-ad)**
66+
6267
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
6368

69+
## Perform Initial Configuration of the Mist Cloud SSO
70+
71+
1. Sign in to the Mist dashboard using a local account.
72+
2. Go to **Organization > Settings > Single Sign-On > Add IdP**.
73+
3. Under **Single Sign-On** section select **Add IDP**.
74+
4. In the **Name** field type `Azure AD` and select **Add**.
75+
76+
![Screenshot shows to add identity provider.](./media/mist-cloud-admin-tutorial/identity-provider.png)
77+
78+
1. Copy **Reply URL** value, paste this value into the **Reply URL** text box in the **Basic SAML Configuration** section in the Azure portal.
79+
80+
![Screenshot shows to Reply URL value.](./media/mist-cloud-admin-tutorial/reply-url.png)
81+
82+
6483
## Configure Azure AD SSO
6584

6685
Follow these steps to enable Azure AD SSO in the Azure portal.
@@ -101,14 +120,26 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
101120

102121
> [!NOTE]
103122
> Please click [here](../develop/howto-add-app-roles-in-azure-ad-apps.md#app-roles-ui) to know how to configure Role in Azure AD.
123+
> Mist Cloud requires Role attribute to assign correct admin privileges to the user.
104124
105125
1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Certificate (Base64)** and select **Download** to download the certificate and save it on your computer.
106126

107127
![Screenshot shows the Certificate download link.](common/certificatebase64.png "Certificate")
108128

109-
1. On the **Set up Mist Cloud Admin SSO** section, copy the appropriate URL(s) based on your requirement.
129+
1. 8. On the **Set up Mist Cloud Admin SSO** section, copy the appropriate **Login URL** and **Azure AD Identifier**.
130+
131+
![Screenshot shows to copy configuration appropriate URL.](common/copy-configuration-urls.png "Metadata")
132+
133+
### Create Role for the SSO Application
134+
135+
In this section, you'll create a Superuser Role to later assign it to test user B.Simon.
136+
137+
1. In the Azure portal, select **App Registrations**, and then select **All Applications**.
138+
2. In the applications list, select **Mist Cloud Admin SSO**.
139+
3. In the app's overview page, find the **Manage** section and select **App Roles**.
140+
4. Select **Create App Role**, then type **Mist Superuser** in the **Display Name** field.
141+
5. Type **Superuser** in the **Value** field, then type **Mist Superuser Role** in the **Description** field, then select **Apply**.
110142

111-
![Screenshot shows to copy configuration appropriate URL.](common/copy-configuration-urls.png "Metadata")
112143

113144
### Create an Azure AD test user
114145

@@ -131,36 +162,32 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
131162
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
132163
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
133164
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.
134-
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.
165+
1. 6. Click Select a **Role**, then select **Mist Superuser** and click **Select**.
135166
1. In the **Add Assignment** dialog, click the **Assign** button.
136167

137-
## Configure Mist Cloud Admin SSO
138-
139-
1. Log in to your Mist Cloud Admin SSO company site as an administrator.
140-
141-
1. Go to **Organization** > **Settings** > **Single Sign-On** > **Add IdP**.
142-
143-
![Screenshot that shows the Configuration Settings.](./media/mist-cloud-admin-tutorial/settings.png "Configuration")
168+
## Complete configuration of the Mist Cloud
144169

145170
1. In the **Create Identity Provider** section, perform the following steps:
146171

147-
![Screenshot that shows the Organization Algorithm.](./media/mist-cloud-admin-tutorial/certificate.png "Organization")
172+
![Screenshot that shows the Organization Algorithm.](./media/mist-cloud-admin-tutorial/configure-mist.png "Organization")
148173

149174
1. In the **Issuer** textbox, paste the **Azure AD Identifier** value which you have copied from the Azure portal.
150175

151176
1. Open the downloaded **Certificate (Base64)** from the Azure portal into Notepad and paste the content into the **Certificate** textbox.
152177

153178
1. In the **SSO URL** textbox, paste the **Login URL** value which you have copied from the Azure portal.
154179

155-
1. In the **Custom Logout URL** textbox, paste the **Logout URL** value which you have copied from the Azure portal.
180+
1. Click **Save**.
156181

157-
1. Copy **ACS URL** value, paste this value into the **Reply URL** text box in the **Basic SAML Configuration** section in the Azure portal.
182+
## Create Roles to link roles sent by the Azure AD
158183

159-
1. Click **Save**.
184+
1. In the Mist dashboard navigate to **Organization > Settings**. Under **Single Sign-On** section, select **Create Role**.
160185

161-
### Create Mist Cloud Admin SSO test user
186+
![Screenshot that shows the Create Role section.](./media/mist-cloud-admin-tutorial/create-role.png)
162187

163-
In this section, you create a user called Britta Simon at Mist Cloud Admin SSO. Work with [Mist Cloud Admin SSO support team](mailto:[email protected]) to add the users in the Mist Cloud Admin SSO platform. Users must be created and activated before you use single sign-on.
188+
1. Role name must match Role claim value sent by Azure AD, for example type `Superuser` in the **Name** field, specify desired admin privileges for the role and select **Create**.
189+
190+
![Screenshot that shows the Create Role button.](./media/mist-cloud-admin-tutorial/create-button.png)
164191

165192
## Test SSO
166193

@@ -172,6 +199,9 @@ In this section, you test your Azure AD single sign-on configuration with follow
172199

173200
* Go to Mist Cloud Admin SSO Sign-on URL directly and initiate the login flow from there.
174201

202+
> [!NOTE]
203+
> For each user first login must be performed from the IdP prior to using SP initiated flow.
204+
175205
#### IDP initiated:
176206

177207
* Click on **Test this application** in Azure portal and you should be automatically signed in to the Mist Cloud Admin SSO for which you set up the SSO.
@@ -180,4 +210,4 @@ You can also use Microsoft My Apps to test the application in any mode. When you
180210

181211
## Next steps
182212

183-
Once you configure Mist Cloud Admin SSO 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 Cloud App Security](/cloud-app-security/proxy-deployment-aad).
213+
Once you configure Mist Cloud Admin SSO 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 Cloud App Security](/cloud-app-security/proxy-deployment-aad).

0 commit comments

Comments
 (0)