You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/external-identities/authentication-conditional-access.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ When an Azure AD organization shares resources with external users with an ident
46
46
47
47
The following diagram illustrates the authentication flow when an external user signs in with an account from a non-Azure AD identity provider, such as Google, Facebook, or a federated SAML/WS-Fed identity provider.
48
48
49
-
[](media/authentication-conditional-access/authentication-flow-b2b-guests.png#lightbox))
49
+
[](media/authentication-conditional-access/authentication-flow-b2b-guests.png#lightbox)
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/secure-external-access-resources.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Both methods have drawbacks. For more information, see the following table.
39
39
| Area of concern | Local credentials | Federation |
40
40
|----|---|---|
41
41
| Security | - Access continues after external user terminates<br> - UserType is Member by default, which grants too much default access | - No user-level visibility <br> - Unknown partner security posture|
42
-
| Expense | - Password and multi-factor authentication (MFA) management<br> - Onboarding process<br> - Identity cleanup<br> - Overhead of running a separate directory | Small partners can't afford the infrastructure, lack expertise, and might user consumer email|
42
+
| Expense | - Password and multi-factor authentication (MFA) management<br> - Onboarding process<br> - Identity cleanup<br> - Overhead of running a separate directory | Small partners can't afford the infrastructure, lack expertise, and might use consumer email|
43
43
| Complexity | Partner users manage more credentials | Complexity grows with each new partner, and increased for partners|
44
44
45
45
Azure Active Directory (Azure AD) B2B integrates with other tools in Azure AD, and Microsoft 365 services. Azure AD B2B simplifies collaboration, reduces expense, and increases security.
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/whats-new.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,8 +79,8 @@ For more information, see:
79
79
**Service category:** Group Management
80
80
**Product capability:** End User Experiences
81
81
82
-
A new and improved My Groups experience is now available at https://www.myaccount.microsoft.com/groups. My Groups enables end users to easily manage groups, such as finding groups to join, managing groups they own, and managing existing group memberships. Based on customer feedback, the new My Groups support sorting and filtering on lists of groups and group members, a full list of group members in large groups, and an actionable overview page for membership requests.
83
-
This experience replaces the existing My Groups experience at https://www.mygroups.microsoft.com in May.
82
+
A new and improved My Groups experience is now available at `https://www.myaccount.microsoft.com/groups`. My Groups enables end users to easily manage groups, such as finding groups to join, managing groups they own, and managing existing group memberships. Based on customer feedback, the new My Groups support sorting and filtering on lists of groups and group members, a full list of group members in large groups, and an actionable overview page for membership requests.
83
+
This experience replaces the existing My Groups experience at `https://www.mygroups.microsoft.com` in May.
84
84
85
85
86
86
For more information, see: [Update your Groups info in the My Apps portal](https://support.microsoft.com/account-billing/update-your-groups-info-in-the-my-apps-portal-bc0ca998-6d3a-42ac-acb8-e900fb1174a4).
|**`<region>.dp.kubernetesconfiguration.azure.com`**|**`HTTPS:443`**| This address is used to fetch configuration information from the Cluster Extensions service and report extension status to the service.|
213
213
|**`mcr.microsoft.com, *.data.mcr.microsoft.com`**|**`HTTPS:443`**| This address is required to pull container images for installing cluster extension agents on AKS cluster.|
214
+
|**`arcmktplaceprod.azurecr.io`**|**`HTTPS:443`**|This address is required to pull container images for installing marketplace extensions on AKS cluster.|
215
+
|**`*.ingestion.msftcloudes.com, *.microsoftmetrics.com`**|**`HTTPS:443`**|This address is used to send agents metrics data to Azure.|
216
+
|**`marketplaceapi.microsoft.com`**|**`HTTPS: 443`**|This address is used to send custom meter-based usage to the commerce metering API.|
214
217
215
218
#### Azure US Government required FQDN / application rules
0 commit comments