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/app-service/configure-authentication-provider-aad.md
+20-36Lines changed: 20 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,29 +24,30 @@ Follow these best practices when setting up your app and authentication:
24
24
## <aname="express"> </a>Configure with express settings
25
25
26
26
1. In the [Azure portal], search for and select **App Services**, and then select your app.
27
-
1. In the left pane, under **Settings** select **Authentication / Authorization** and make sure that **App Service Authentication** is **On**.
28
-
1. Select **Azure Active Directory**, and then under **Management Mode** select **Express**.
29
-
1. Select **OK** to register the App Service app in Azure Active Directory. A new app registration is created.
27
+
2. From the left navigation, select **Authentication / Authorization** > **On**.
28
+
3. Select **Azure Active Directory** > **Express**.
30
29
31
30
If you want to choose an existing app registration instead:
32
31
33
-
1. Choose **Select an existing app** and then search for the name of a previously created app registration within your tenant.
34
-
1. Select the app registration and then select **OK**.
35
-
1. Then select **OK** on the Azure Active Directory settings page.
32
+
1. Choose **Select Existing AD app**, then click **Azure AD App**.
33
+
2. Choose an existing app registration and click **OK**.
36
34
37
-
By default, App Service provides authentication but doesn't restrict authorized access to your site content and APIs. You must authorize users in your app code.
38
-
1. (Optional) To restrict app access only to users authenticated by Azure Active Directory, 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 to Azure Active Directory for authentication.
35
+
3. Select **OK** to register the App Service app in Azure Active Directory. A new app registration is created.
36
+
37
+
38
+
39
+
4. (Optional) By default, App Service provides authentication but doesn't restrict authorized access to your site content and APIs. You must authorize users in your app code. To restrict app access only to users authenticated by Azure Active Directory, 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 to Azure Active Directory for authentication.
39
40
40
41
> [!CAUTION]
41
42
> 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, with the app manually starting login itself. For more information, see [Authentication flow](overview-authentication-authorization.md#authentication-flow).
42
-
1. Select **Save**.
43
+
5. Select **Save**.
43
44
44
45
## <aname="advanced"> </a>Configure with advanced settings
45
46
46
-
You can configure app settings manually if you want to use an Azure AD tenant that's different from the one you use to sign in to Azure. To complete this custom configuration, you'll need to:
47
+
You can configure app settings manually if you want to use an app registration from a different Azure AD tenant. To complete this custom configuration:
47
48
48
49
1. Create a registration in Azure AD.
49
-
1. Provide some of the registration details to App Service.
50
+
2. Provide some of the registration details to App Service.
50
51
51
52
### <aname="register"> </a>Create an app registration in Azure AD for your App Service app
52
53
@@ -62,7 +63,7 @@ Perform the following steps:
62
63
1. Sign in to the [Azure portal], search for and select **App Services**, and then select your app. Note your app's **URL**. You'll use it to configure your Azure Active Directory app registration.
1. In the **Register an application** page, enter a **Name** for your app registration.
65
-
1. In **Redirect URI**, select **Web** and enter the URL of your App Service app and append the path `/.auth/login/aad/callback`. For example, `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
66
+
1. In **Redirect URI**, select **Web** and type `<app-url>/.auth/login/aad/callback`. For example, `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
66
67
1. Select **Create**.
67
68
1. After the app registration is created, copy the **Application (client) ID** and the **Directory (tenant) ID** for later.
68
69
1. Select **Branding**. In **Home page URL**, enter the URL of your App Service app and select **Save**.
@@ -78,24 +79,22 @@ Perform the following steps:
78
79
1. (Optional) To create a client secret, select **Certificates & secrets** > **New client secret** > **Add**. Copy the client secret value shown in the page. It won't be shown again.
79
80
1. (Optional) To add multiple **Reply URLs**, select **Authentication**.
80
81
81
-
### <aname="secrets"> </a>Add Azure Active Directory information to your App Service app
82
+
### <aname="secrets"> </a>Enable Azure Active Directory in your App Service app
82
83
83
84
1. In the [Azure portal], search for and select **App Services**, and then select your app.
84
-
1. In the left pane, under **Settings**, select **Authentication / Authorization**and make sure that **App Service Authentication** is**On**.
85
+
1. In the left pane, under **Settings**, select **Authentication / Authorization**>**On**.
85
86
1. (Optional) By default, App Service authentication allows unauthenticated access to your app. To enforce user authentication, set **Action to take when request is not authenticated** to **Log in with Azure Active Directory**.
86
-
1. Under Authentication Providers, select **Azure Active Directory**.
87
+
1. Under **Authentication Providers**, select **Azure Active Directory**.
87
88
1. In **Management mode**, select **Advanced** and configure App Service authentication according to the following table:
88
89
89
90
|Field|Description|
90
91
|-|-|
91
92
|Client ID| Use the **Application (client) ID** of the app registration. |
92
93
|Issuer ID| Use `https://login.microsoftonline.com/<tenant-id>`, and replace *\<tenant-id>* with the **Directory (tenant) ID** of the app registration. |
93
94
|Client Secret (Optional)| Use the client secret you generated in the app registration.|
94
-
|Allowed Token Audiences| If this is a cloud or server app and you want to allow authentication tokens from a web app, add the **Application ID URI** of the web app here. |
95
+
|Allowed Token Audiences| If this is a cloud or server app and you want to allow authentication tokens from a web app, add the **Application ID URI** of the web app here. The configured **Client ID** is *always* implicitly considered to be an allowed audience. |
95
96
96
-
> [!NOTE]
97
-
> The configured **Client ID** is *always* implicitly considered to be an allowed audience, regardless of how you configured the **Allowed Token Audiences**.
98
-
1. Select **OK**, and then select **Save**.
97
+
2. Select **OK**, and then select **Save**.
99
98
100
99
You're now ready to use Azure Active Directory for authentication in your App Service app.
101
100
@@ -105,11 +104,11 @@ You can register native clients to allow authentication using a client library s
105
104
106
105
1. In the [Azure portal], select **Active Directory** > **App registrations** > **New registration**.
107
106
1. In the **Register an application** page, enter a **Name** for your app registration.
108
-
1. In **Redirect URI**, select **Public client (mobile & desktop)** and enter the URL of your App Service app and append the path `/.auth/login/aad/callback`. For example, `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
109
-
1. Select **Create**.
107
+
1. In **Redirect URI**, select **Public client (mobile & desktop)** and type the URL `<app-url>/.auth/login/aad/callback`. For example, `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
110
108
111
109
> [!NOTE]
112
110
> For a Windows application, use the [package SID](../app-service-mobile/app-service-mobile-dotnet-how-to-use-client-library.md#package-sid) as the URI instead.
111
+
1. Select **Create**.
113
112
1. After the app registration is created, copy the value of **Application (client) ID**.
1. Select the app registration you created earlier for your App Service app. If you don't see the app registration, make sure that you've added the **user_impersonation** scope in [Create an app registration in Azure AD for your App Service app](#register).
@@ -121,21 +120,6 @@ You have now configured a native client application that can access your App Ser
Copy file name to clipboardExpand all lines: articles/batch/batch-task-output-file-conventions.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ If your scenario differs from those listed above, you may need to consider a dif
42
42
43
43
## What is the Batch File Conventions standard?
44
44
45
-
The [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/psSdkJson6/src/SDKs/Batch/Support/FileConventions#conventions) provides a naming scheme for the destination containers and blob paths to which your output files are written. Files persisted to Azure Storage that adhere to the File Conventions standard are automatically available for viewing in the Azure portal. The portal is aware of the naming convention and so can display files that adhere to it.
45
+
The [Batch File Conventions standard](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/batch/Microsoft.Azure.Batch.Conventions.Files) provides a naming scheme for the destination containers and blob paths to which your output files are written. Files persisted to Azure Storage that adhere to the File Conventions standard are automatically available for viewing in the Azure portal. The portal is aware of the naming convention and so can display files that adhere to it.
46
46
47
47
The File Conventions library for .NET automatically names your storage containers and task output files according to the File Conventions standard. The File Conventions library also provides methods to query output files in Azure Storage according to job ID, task ID, or purpose.
48
48
@@ -224,15 +224,15 @@ The [source code][github_file_conventions] for the File Conventions library is a
224
224
- See [Persist task data to Azure Storage with the Batch service API](batch-task-output-files.md) to learn how to use the Batch service API to persist output data.
0 commit comments