Skip to content

Commit 1e817ae

Browse files
juntakatamsmimart
andauthored
Update articles/active-directory/manage-apps/tenant-restrictions.md
Looks great! Co-Authored-By: Michele Martin <[email protected]>
1 parent be64b92 commit 1e817ae

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ While configuration of tenant restrictions is done on the corporate proxy infras
102102
The admin for the tenant specified as the Restricted-Access-Context tenant can use this report to see sign-ins blocked because of the tenant restrictions policy, including the identity used and the target directory ID. Sign-ins are included if the tenant setting the restriction is either the user tenant or resource tenant for the sign-in.
103103

104104
> [!NOTE]
105-
> The report may contain limited information such as target directory ID when users in tenant other than specified as the Restricted-Access-Context tenant sign in. In this case, user identity such as name and user principal name are masked to protect user data in other tenants.
105+
> The report may contain limited information, such as target directory ID, when a user who is in a tenant other than the Restricted-Access-Context tenant signs in. In this case, user identifiable information, such as name and user principal name, is masked to protect user data in other tenants.
106106
107107
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:
108108

0 commit comments

Comments
 (0)