Skip to content

Commit 2a75021

Browse files
committed
Merge branch 'release-preview-private-5g-core-june' of https://github.com/MicrosoftDocs/azure-docs-pr into sim-group-fix
2 parents e33f240 + a909f2d commit 2a75021

File tree

652 files changed

+6992
-3319
lines changed

Some content is hidden

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

652 files changed

+6992
-3319
lines changed

.openpublishing.redirection.active-directory.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10801,6 +10801,16 @@
1080110801
"redirect_url": "/azure/active-directory/manage-apps/add-application-portal",
1080210802
"redirect_document_id": false
1080310803
},
10804+
{
10805+
"source_path": "articles/active-directory/saas-apps/iprova-provisioning-tutorial.md",
10806+
"redirect_url": "/azure/active-directory/saas-apps/zenya-provisioning-tutorial",
10807+
"redirect_document_id": false
10808+
},
10809+
{
10810+
"source_path": "articles/active-directory/saas-apps/iprova-tutorial.md",
10811+
"redirect_url": "/azure/active-directory/saas-apps/zenya-tutorial",
10812+
"redirect_document_id": false
10813+
},
1080410814
{
1080510815
"source_path": "articles/active-directory/manage-apps/manage-certificates-for-federated-single-sign-on.md",
1080610816
"redirect_url": "/azure/active-directory/manage-apps/tutorial-manage-certificates-for-federated-single-sign-on",

.openpublishing.redirection.azure-monitor.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/azure-monitor/change/change-analysis-powershell.md",
5+
"redirect_url": "/azure/azure-monitor/change/change-analysis",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger.md",
510
"redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger",

.openpublishing.redirection.defender-for-iot.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/defender-for-iot/organizations/appliance-catalog/appliance-catalog-overview.md",
5+
"redirect_url": "/azure/defender-for-iot/organizations/appliance-catalog/index",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/defender-for-iot/organizations/plan-network-monitoring.md",
510
"redirect_url": "/azure/defender-for-iot/organizations/best-practices/plan-network-monitoring",

articles/active-directory/app-provisioning/how-provisioning-works.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -74,13 +74,13 @@ You can use scoping filters to define attribute-based rules that determine which
7474

7575
### B2B (guest) users
7676

77-
It's possible to use the Azure AD user provisioning service to provision B2B (or guest) users in Azure AD to SaaS applications.
77+
It's possible to use the Azure AD user provisioning service to provision B2B (guest) users in Azure AD to SaaS applications.
7878
However, for B2B users to sign in to the SaaS application using Azure AD, the SaaS application must have its SAML-based single sign-on capability configured in a specific way. For more information on how to configure SaaS applications to support sign-ins from B2B users, see [Configure SaaS apps for B2B collaboration](../external-identities/configure-saas-apps.md).
7979

8080
> [!NOTE]
81-
> The userPrincipalName for a guest user is often displayed as "alias#EXT#@domain.com". When the userPrincipalName is included in your attribute mappings as a source attribute, the #EXT# is stripped from the userPrincipalName. If you require the #EXT# to be present, replace userPrincipalName with originalUserPrincipalName as the source attribute.
82-
userPrincipalName = alias@domain.com
83-
originalUserPrincipalName = alias#EXT#@domain.com
81+
> The userPrincipalName for a B2B user represents the external user's email address alias@theirdomain as "alias_theirdomain#EXT#@yourdomain". When the userPrincipalName attribute is included in your attribute mappings as a source attribute, and a B2B user is being provisioned, the #EXT# and your domain is stripped from the userPrincipalName, so only their original alias@theirdomain is used for matching or provisioning. If you require the full user principal name including #EXT# and your domain to be present, replace userPrincipalName with originalUserPrincipalName as the source attribute. <br />
82+
userPrincipalName = alias@theirdomain<br />
83+
originalUserPrincipalName = alias_theirdomain#EXT#@yourdomain
8484

8585
## Provisioning cycles: Initial and incremental
8686

articles/active-directory/authentication/feature-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ This following tables list Azure AD feature availability in Azure Government.
3333
|| Service-level agreement | &#x2705; |
3434
|**Applications access**|SaaS apps with modern authentication (Azure AD application gallery apps, SAML, and OAUTH 2.0) | &#x2705; |
3535
|| Group assignment to applications | &#x2705; |
36-
|| Cloud app discovery (Microsoft Cloud App Security) | &#x2705; |
36+
|| Cloud app discovery (Microsoft Defender for Cloud Apps) | &#x2705; |
3737
|| Application Proxy for on-premises, header-based, and Integrated Windows Authentication | &#x2705; |
3838
|| Secure hybrid access partnerships (Kerberos, NTLM, LDAP, RDP, and SSH authentication) | &#x2705; |
3939
|**Authorization and Conditional Access**|Role-based access control (RBAC) | &#x2705; |

0 commit comments

Comments
 (0)