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/claimsproviders.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
@@ -48,7 +48,7 @@ The **ClaimsProvider** element contains the following child elements:
48
48
| Element | Occurrences | Description |
49
49
| ------- | ---------- | ----------- |
50
50
| Domain | 0:1 | A string that contains the domain name for the claim provider. For example, if your claims provider includes the Facebook technical profile, the domain name is Facebook.com. This domain name is used for all technical profiles defined in the claims provider unless overridden by the technical profile. The domain name can also be referenced in a **domain_hint**. For more information, see the **Redirect sign-in to a social provider** section of [Set up direct sign-in using Azure Active Directory B2C](direct-signin.md). |
51
-
| DisplayName |0:1 | A string that contains the name of the claims provider that can be displayed to users. |
51
+
| DisplayName |1:1 | A string that contains the name of the claims provider that can be displayed to users. |
52
52
|[TechnicalProfiles](technicalprofiles.md)| 0:1 | A set of technical profiles supported by the claim provider |
53
53
54
54
**ClaimsProvider** organizes how your technical profiles relate to the claims provider. The following example shows the Azure Active Directory claims provider with the Azure Active Directory technical profiles:
Copy file name to clipboardExpand all lines: articles/app-service/configure-authentication-provider-aad.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,6 @@ ms.custom: fasttrack-edit
15
15
16
16
This article shows you how to configure Azure App Service to use Azure Active Directory (Azure AD) as an authentication provider.
17
17
18
-
> [!NOTE]
19
-
> At this time, Azure App Service and Azure Functions are only supported by Azure AD v1.0. They're not supported by the [Microsoft identity platform v2.0](https://docs.microsoft.com/azure/active-directory/develop/v2-overview), which includes Microsoft Authentication Libraries (MSAL).
20
-
21
18
Follow these best practices when setting up your app and authentication:
22
19
23
20
- Give each App Service app its own permissions and consent.
This topic shows you how to configure Azure App Service to use Microsoft Account as an authentication provider.
16
+
This topic shows you how to configure Azure App Service to use AAD to support personal Microsoft account logins.
17
+
18
+
> [!NOTE]
19
+
> Both personal Microsoft accounts and organizational accounts use the AAD identity provider. At this time, is not possible to configure this identity provider to support both types of log-ins.
17
20
18
21
## <aname="register-microsoft-account"> </a>Register your app with Microsoft Account
19
22
20
23
1. Go to [**App registrations**](https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade) in the Azure portal. If needed, sign in with your Microsoft account.
21
24
1. Select **New registration**, then enter an application name.
22
-
1. In **Redirect URIs**, select **Web**, and then enter `https://<app-domain-name>/.auth/login/microsoftaccount/callback`. Replace *\<app-domain-name>* with the domain name of your app. For example, `https://contoso.azurewebsites.net/.auth/login/microsoftaccount/callback`. Be sure to use the HTTPS scheme in the URL.
25
+
1. Under **Supported account types**, select **Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)**
26
+
1. In **Redirect URIs**, select **Web**, and then enter `https://<app-domain-name>/.auth/login/aad/callback`. Replace *\<app-domain-name>* with the domain name of your app. For example, `https://contoso.azurewebsites.net/.auth/login/aad/callback`. Be sure to use the HTTPS scheme in the URL.
23
27
24
28
1. Select **Register**.
25
29
1. Copy the **Application (Client) ID**. You'll need it later.
@@ -33,12 +37,12 @@ This topic shows you how to configure Azure App Service to use Microsoft Account
33
37
34
38
1. Go to your application in the [Azure portal].
35
39
1. Select **Settings** > **Authentication / Authorization**, and make sure that **App Service Authentication** is **On**.
36
-
1. Under **Authentication Providers**, select **Microsoft Account**. Paste in the Application (client) ID and client secret that you obtained earlier. Enable any scopes needed by your application.
40
+
1. Under **Authentication Providers**, select **Azure Active Directory**. Select **Advanced** under **Management mode**. Paste in the Application (client) ID and client secret that you obtained earlier. Use **https://login.microsoftonline.com/9188040d-6c67-4c5b-b112-36a304b66dad/v2.0** for the **Issuer Url** field.
37
41
1. Select **OK**.
38
42
39
43
App Service provides authentication, but doesn't restrict authorized access to your site content and APIs. You must authorize users in your app code.
40
44
41
-
1. (Optional) To restrict access to Microsoft account users, set **Action to take when request is not authenticated** to **Log in with Microsoft Account**. When you set this functionality, your app requires all requests to be authenticated. It also redirects all unauthenticated requests to Microsoft account for authentication.
45
+
1. (Optional) To restrict access to Microsoft account users, set **Action to take when request is not authenticated** to **Log in with Azure Active Directory**. When you set this functionality, your app requires all requests to be authenticated. It also redirects all unauthenticated requests to use AAD for authentication. Note that becuase you have configured your **Issuer Url** to use the Microsoft Account tenant, only personal acccounts will successfully authenticate.
42
46
43
47
> [!CAUTION]
44
48
> Restricting access in this way applies to all calls to your app, which might not be desirable for apps that have a publicly available home page, as in many single-page applications. For such applications, **Allow anonymous requests (no action)** might be preferred so that the app manually starts authentication itself. For more information, see [Authentication flow](overview-authentication-authorization.md#authentication-flow).
|**Azure Data Lake Storage Gen2**| Microsoft.Storage/storageAccounts | Blob (blob, blob_secondary) |
55
+
|**Azure Data Lake Storage Gen2**| Microsoft.Storage/storageAccounts | Blob (blob, blob_secondary)<BR> Data Lake File System Gen2 (dfs, dfs_secondary)|
Copy file name to clipboardExpand all lines: includes/azure-subscription-limits-azure-resource-manager.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,16 +16,17 @@
16
16
| VM total cores per [subscription](../articles/billing-buy-sign-up-azure-subscription.md)|20<sup>1</sup> per region. | Contact support. |
17
17
| Azure Spot VM total cores per [subscription](../articles/billing-buy-sign-up-azure-subscription.md)|20<sup>1</sup> per region. | Contact support. |
18
18
| VM per series, such as Dv2 and F, cores per [subscription](../articles/billing-buy-sign-up-azure-subscription.md)|20<sup>1</sup> per region. | Contact support. |
19
-
|[Coadministrators](../articles/cost-management-billing/manage/add-change-subscription-administrator.md) per subscription |Unlimited. |Unlimited. |
20
19
|[Storage accounts](../articles/storage/common/storage-account-create.md) per region per subscription |250 |250 |
21
-
|[Resource groups](../articles/azure-resource-manager/management/overview.md) per subscription |980 |980 |
22
20
|[Availability sets](../articles/virtual-machines/windows/manage-availability.md#configure-multiple-virtual-machines-in-an-availability-set-for-redundancy) per subscription |2,000 per region. |2,000 per region. |
21
+
|[Affinity groups](../articles/virtual-network/virtual-networks-migrate-to-regional-vnet.md) per subscription |N/A<sup>3</sup> |N/A<sup>3</sup> |
22
+
|[Cloud services](../articles/cloud-services/cloud-services-choose-me.md) per subscription |N/A<sup>3</sup> |N/A<sup>3</sup> |
23
+
|[Resource groups](../articles/azure-resource-manager/management/overview.md) per subscription |980 |980 |
| Tags per subscription<sup>2</sup> |Unlimited. |Unlimited. |
25
26
| Unique tag calculations per subscription<sup>2</sup> | 10,000 | 10,000 |
26
-
|[Cloud services](../articles/cloud-services/cloud-services-choose-me.md) per subscription |N/A<sup>3</sup> |N/A<sup>3</sup> |
27
-
|[Affinity groups](../articles/virtual-network/virtual-networks-migrate-to-regional-vnet.md) per subscription |N/A<sup>3</sup> |N/A<sup>3</sup> |
28
27
|[Subscription-level deployments](../articles/azure-resource-manager/templates/deploy-to-subscription.md) per location | 800<sup>4</sup> | 800 |
28
+
| Subscriptions per Azure Active Directory tenant | Unlimited. | Unlimited. |
29
+
|[Coadministrators](../articles/cost-management-billing/manage/add-change-subscription-administrator.md) per subscription |Unlimited. |Unlimited. |
29
30
30
31
<sup>1</sup>Default limits vary by offer category type, such as Free Trial and Pay-As-You-Go, and by series, such as Dv2, F, and G. For example, the default for Enterprise Agreement subscriptions is 350.
0 commit comments