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-b2c/partner-cloudflare.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
@@ -42,7 +42,7 @@ After a custom domain for Azure AD B2C is configured using Azure Front Door, [te
42
42
43
43
## Create a Cloudflare account
44
44
45
-
On cloudflare.com, you can [create an account](https://dash.cloudflare.com/sign-up). To enable WAF, on [Application Services]([https://www.cloudflare.com/plans/](https://www.cloudflare.com/plans/#price-matrix) select **Pro**, which is required.
45
+
On cloudflare.com, you can [create an account](https://dash.cloudflare.com/sign-up). To enable WAF, on [Application Services](https://www.cloudflare.com/plans/#price-matrix), select **Pro**, which is required.
Copy file name to clipboardExpand all lines: articles/active-directory/app-provisioning/insufficient-access-rights-error-troubleshooting.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
@@ -75,7 +75,7 @@ Reference articles that explain the reason in detail:
75
75
76
76
If option 1 is not feasible and doesn't work as expected, then ask Cx to check with their AD admin and security administrators, if they are allowed to modify the default permissions of the ```AdminSDHolder``` container. This [article](https://go.microsoft.com/fwlink/?linkid=2240198) that explains the importance of the ```AdminSDHolder``` container. Once Cx gets internal approval to update the ```AdminSDHolder``` container permissions, there are two ways to update the permissions.
77
77
78
-
* Using ```ADSIEdit``` as described in this [article](https://petri.com/active-directory-security-understanding-adminsdholder-object).
78
+
* Using ```ADSIEdit``` as described in this [article](https://petri.com/active-directory-security-understanding-adminsdholder-object).
79
79
* Using ```DSACLS``` command-line script. Here's an example script that could be used as a starting point and Cx can tweak it as per their requirements.
Copy file name to clipboardExpand all lines: articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,9 +53,9 @@ The **core** user schema only requires three attributes (all other attributes ar
53
53
-`userName`, a unique identifier for the user (generally maps to the Azure AD user principal name)
54
54
-`meta`, *read-only* metadata maintained by the service provider
55
55
56
-
In addition to the **core** user schema, the SCIM standard defines an **enterprise** user extension with a model for extending the user schema to meet your application’s needs.
56
+
In addition to the **core** user schema, the SCIM standard defines an **enterprise** user extension with a model for extending the user schema to meet your application's needs.
57
57
58
-
For example, if your application requires both a user's email and user’s manager, use the **core** schema to collect the user’s email and the **enterprise** user schema to collect the user’s manager.
58
+
For example, if your application requires both a user's email and user's manager, use the **core** schema to collect the user's email and the **enterprise** user schema to collect the user's manager.
59
59
60
60
To design your schema, follow these steps:
61
61
@@ -72,7 +72,7 @@ The following table lists an example of required attributes:
|status|active|isSoftDeleted (computed value not stored on user)|
@@ -933,7 +933,7 @@ The open source .NET Core [reference code example](https://aka.ms/SCIMReferenceC
933
933
934
934
The solution is composed of two projects, _Microsoft.SCIM_ and _Microsoft.SCIM.WebHostSample_.
935
935
936
-
The _Microsoft.SCIM_ project is the library that defines the components of the web service that conforms to the SCIM specification. It declares the interface _Microsoft.SCIM.IProvider_, requests are translated into calls to the provider’s methods, which would be programmed to operate on an identity store.
936
+
The _Microsoft.SCIM_ project is the library that defines the components of the web service that conforms to the SCIM specification. It declares the interface _Microsoft.SCIM.IProvider_, requests are translated into calls to the provider's methods, which would be programmed to operate on an identity store.
937
937
938
938

939
939
@@ -992,7 +992,7 @@ Requests from Azure AD Provisioning Service include an OAuth 2.0 bearer token. A
@@ -1031,7 +1031,7 @@ A bearer token is also required to use of the provided [Postman tests](https://g
1031
1031
1032
1032
For more information on multiple environments in ASP.NET Core, see [Use multiple environments in ASP.NET Core](/aspnet/core/fundamentals/environments).
1033
1033
1034
-
The following code enforces that requests to any of the service’s endpoints are authenticated using a bearer token signed with a custom key:
1034
+
The following code enforces that requests to any of the service's endpoints are authenticated using a bearer token signed with a custom key:
AzureADchecksthecurrentattributevalueintheidentitystorebeforeupdatingit. However, onlythemanagerattributeisthecheckedfirstforusers. Here'sanexampleofarequesttodeterminewhetherthemanagerattributeofauserobjectcurrentlyhasacertainvalue:
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/how-to-migrate-mfa-server-to-mfa-with-federation.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
@@ -175,7 +175,7 @@ This section covers final steps before migrating user MFA settings.
175
175
176
176
### Set federatedIdpMfaBehavior to enforceMfaByFederatedIdp
177
177
178
-
For federated domains, MFA may be enforced by Azure AD Conditional Access or by the on-premises federation provider. Each federated domain has a Microsoft Graph PowerShell security setting named **federatedIdpMfaBehavior**. You can set **federatedIdpMfaBehavior** to `enforceMfaByFederatedIdp` so Azure AD accepts MFA that's performed by the federated identity provider. If the federated identity provider didn't perform MFA, Azure AD redirects the request to the federated identity provider to perform MFA. For more information, see [federatedIdpMfaBehavior](/graph/api/resources/internaldomainfederation?view=graph-rest-beta#federatedidpmfabehavior-values&preserve-view=true).
178
+
For federated domains, MFA may be enforced by Azure AD Conditional Access or by the on-premises federation provider. Each federated domain has a Microsoft Graph PowerShell security setting named **federatedIdpMfaBehavior**. You can set **federatedIdpMfaBehavior** to `enforceMfaByFederatedIdp` so Azure AD accepts MFA that's performed by the federated identity provider. If the federated identity provider didn't perform MFA, Azure AD redirects the request to the federated identity provider to perform MFA. For more information, see [federatedIdpMfaBehavior](/graph/api/resources/internaldomainfederation?view=graph-rest-beta#federatedidpmfabehavior-values&preserve-view=true).
179
179
180
180
>[!NOTE]
181
181
> The **federatedIdpMfaBehavior** setting is a new version of the **SupportsMfa** property of the [New-MgDomainFederationConfiguration](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration) cmdlet.
> 
65
+
> :::image type="content" source="media/quickstart-v2-aspnet-core-webapp/aspnetcorewebapp-intro.svg" alt-text="Diagram that how the sample app generated by this quickstart works.":::
Copy file name to clipboardExpand all lines: articles/active-directory/enterprise-users/signin-account-support.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
@@ -27,7 +27,7 @@ You can tell if the sign-in page your organization uses supports Microsoft accou
27
27
28
28

29
29
30
-
[Additional sign-in options work only for personal Microsoft accounts](https://azure.microsoft.com/updates/microsoft-account-signin-options/) but can't be used for signing in to work or school account resources.
30
+
[Additional sign-in options work only for personal Microsoft accounts](https://azure.microsoft.com/updates/microsoft-account-signin-options/) but can't be used for signing in to work or school account resources.
Copy file name to clipboardExpand all lines: articles/active-directory/external-identities/direct-federation.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
@@ -286,7 +286,7 @@ To remove a configuration for an IdP in the Microsoft Entra admin center:
286
286
287
287
1. Select **OK** to confirm deletion.
288
288
289
-
You can also remove federation using the Microsoft Graph API [samlOrWsFedExternalDomainFederation](/graph/api/resources/samlorwsfedexternaldomainfederation?view=graph-rest-beta&preserve-view=true) resource type.
289
+
You can also remove federation using the Microsoft Graph API [samlOrWsFedExternalDomainFederation](/graph/api/resources/samlorwsfedexternaldomainfederation?view=graph-rest-beta&preserve-view=true) resource type.
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/faq.yml
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,7 @@ sections:
28
28
- question: |
29
29
Why do I get "No subscriptions found" when I try to access Azure AD in the Azure portal?
30
30
answer: |
31
-
To access the Azure portal, each user needs permissions with an Azure subscription. If you don't have a paid Microsoft 365 or Azure AD subscription, you will need to activate a free [Azure account](https://azure.microsoft.com/free/
32
-
) or a paid subscription.
31
+
To access the Azure portal, each user needs permissions with an Azure subscription. If you don't have a paid Microsoft 365 or Azure AD subscription, you will need to activate a free [Azure account](https://azure.microsoft.com/free/) or a paid subscription.
0 commit comments