Skip to content

Commit 01af89f

Browse files
authored
Merge pull request #153435 from hpsin/master
Add error UX to TRv1 page
2 parents 53aef5e + 8a3ea15 commit 01af89f

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed
17.4 KB
Loading

articles/active-directory/manage-apps/tenant-restrictions.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-mgmt
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 2/23/2021
11+
ms.date: 4/6/2021
1212
ms.author: kenwith
1313
ms.reviewer: hpsin
1414
ms.collection: M365-identity-device-management
@@ -92,6 +92,8 @@ This section describes the experience for both end users and admins.
9292

9393
An example user is on the Contoso network, but is trying to access the Fabrikam instance of a shared SaaS application like Outlook online. If Fabrikam is a non-permitted tenant for the Contoso instance, the user sees an access denial message, which says you're trying to access a resource that belongs to an organization unapproved by your IT department.
9494

95+
![Tenant restrictions error message, from April 2021](./media/tenant-restrictions/error-message.png)
96+
9597
### Admin experience
9698

9799
While configuration of tenant restrictions is done on the corporate proxy infrastructure, admins can access the tenant restrictions reports in the Azure portal directly. To view the reports:
@@ -108,14 +110,14 @@ The report may contain limited information, such as target directory ID, when a
108110

109111
Like other reports in the Azure portal, you can use filters to specify the scope of your report. You can filter on a specific time interval, user, application, client, or status. If you select the **Columns** button, you can choose to display data with any combination of the following fields:
110112

111-
- **User** - this field can have personally identifiable information removed, where it will be set to `00000000-0000-0000-0000-000000000000`.
113+
- **User** - this field can have personal data removed, where it will be set to `00000000-0000-0000-0000-000000000000`.
112114
- **Application**
113115
- **Status**
114116
- **Date**
115117
- **Date (UTC)** - where UTC is Coordinated Universal Time
116118
- **IP Address**
117119
- **Client**
118-
- **Username** - this field can have personally identifiable information removed, where it will be set to `{PII Removed}@domain.com`
120+
- **Username** - this field can have personal data removed, where it will be set to `{PII Removed}@domain.com`
119121
- **Location**
120122
- **Target tenant ID**
121123

@@ -202,7 +204,7 @@ Some organizations attempt to fix this by blocking `login.live.com` in order to
202204

203205
### Configuration for consumer apps
204206

205-
While the `Restrict-Access-To-Tenants` header functions as an allow-list, the Microsoft account (MSA) block works as a deny signal, telling the Microsoft account platform to not allow users to sign in to consumer applications. To send this signal, the `sec-Restrict-Tenant-Access-Policy` header is injected to traffic visiting `login.live.com` using the same corporate proxy or firewall as [above](#proxy-configuration-and-requirements). The value of the header must be `restrict-msa`. When the header is present and a consumer app is attempting to sign in a user directly, that sign in will be blocked.
207+
While the `Restrict-Access-To-Tenants` header functions as an allowlist, the Microsoft account (MSA) block works as a deny signal, telling the Microsoft account platform to not allow users to sign in to consumer applications. To send this signal, the `sec-Restrict-Tenant-Access-Policy` header is injected to traffic visiting `login.live.com` using the same corporate proxy or firewall as [above](#proxy-configuration-and-requirements). The value of the header must be `restrict-msa`. When the header is present and a consumer app is attempting to sign in a user directly, that sign in will be blocked.
206208

207209
At this time, authentication to consumer applications does not appear in the [admin logs](#admin-experience), as login.live.com is hosted separately from Azure AD.
208210

@@ -219,4 +221,4 @@ The `restrict-msa` policy blocks the use of consumer applications, but allows th
219221
## Next steps
220222

221223
- Read about [Updated Office 365 modern authentication](https://www.microsoft.com/microsoft-365/blog/2015/03/23/office-2013-modern-authentication-public-preview-announced/)
222-
- Review the [Office 365 URLs and IP address ranges](https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2)
224+
- Review the [Office 365 URLs and IP address ranges](https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2)

0 commit comments

Comments
 (0)