Skip to content

Commit b8a2c3e

Browse files
authored
Merge pull request #103191 from KingdomOfEnds/tsi-aad
updated aad
2 parents c556fa1 + e77199d commit b8a2c3e

10 files changed

+21
-9
lines changed

articles/time-series-insights/time-series-insights-authentication-and-authorization.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.reviewer: v-mamcge, jasonh, kfile
1010
ms.devlang: csharp
1111
ms.workload: big-data
1212
ms.topic: conceptual
13-
ms.date: 12/09/2019
13+
ms.date: 02/03/2020
1414
ms.custom: seodec18
1515
---
1616

@@ -88,7 +88,7 @@ Per **step 3**, separating your application's and your user credentials allows y
8888

8989
1. The token can then be passed in the `Authorization` header when the application calls the Time Series Insights API.
9090

91-
* Alternatively, developers may choose to authenticate using MSAL. Read about [migrating to MSAL](https://docs.microsoft.com/azure/active-directory/develop/msal-net-migration) to learn more.
91+
* Alternatively, developers may choose to authenticate using MSAL. Read about [migrating to MSAL](https://docs.microsoft.com/azure/active-directory/develop/msal-net-migration) and see our [Manage GA reference data for an Azure Time Series Insights environment using C#](time-series-insights-manage-reference-data-csharp.md) article to learn more.
9292

9393
## Common headers and parameters
9494

53.3 KB
Loading
807 Bytes
Loading
13.1 KB
Loading
-54.5 KB
Loading
253 KB
Loading
19.7 KB
Loading
6.01 KB
Loading
17.9 KB
Loading

includes/time-series-insights-aad-registration.md

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: time-series-insights
88
author: deepakpalled
99
ms.author: dpalled
1010
manager: cshankar
11-
ms.date: 12/06/2019
11+
ms.date: 02/03/2020
1212
---
1313

1414
1. In the [Azure portal](https://ms.portal.azure.com/), select **Azure Active Directory** > **App registrations** > **New registration**.
@@ -29,18 +29,30 @@ ms.date: 12/06/2019
2929

3030
1. The **Authentication** blade specifies important authentication configuration settings.
3131

32+
1. Add **Redirect URIs** and configure **Access Tokens** by selecting **+ Add a platform**.
33+
34+
1. Determine whether the app is a **public client** or not by selecting **Yes** or **No**.
35+
36+
1. Verify which accounts and tenants are supported.
37+
38+
[![Configure Implicit grant](media/time-series-insights-aad-registration/active-directory-auth-blade.png)](media/time-series-insights-aad-registration/active-directory-auth-blade.png#lightbox)
39+
40+
1. After selecting the appropriate platform, configure your **Redirect URIs** and **Access Tokens** in the side panel to the right of the user interface.
41+
3242
1. **Redirect URIs** must match the address supplied by the authentication request:
3343

34-
* For apps hosted in a local development environment, select **Public client (mobile & desktop)**. Make sure to set the **Default client type** to yes.
35-
* For Single-Page apps hosted on Azure App Service, select **Web**.
44+
* For apps hosted in a local development environment, select **Public client (mobile & desktop)**. Make sure to set **public client** to **Yes**.
45+
* For Single-Page Apps hosted on Azure App Service, select **Web**.
46+
47+
1. Determine whether a **Logout URL** is appropriate.
3648

3749
1. Enable the implicit grant flow by checking **Access tokens** or **ID tokens**.
3850

39-
[![Create Redirect URIs and configure Implicit grant](media/time-series-insights-aad-registration/active-directory-auth-blade.png)](media/time-series-insights-aad-registration/active-directory-auth-blade.png#lightbox)
51+
[![Create Redirect URIs](media/time-series-insights-aad-registration/active-directory-auth-redirect-uri.png)](media/time-series-insights-aad-registration/active-directory-auth-redirect-uri.png#lightbox)
4052

41-
Click **Save**.
53+
Click **Configure**, then **Save**.
4254

43-
1. Select **Certificates & secrets** then **New client secret** to create an application password that client can use to prove its identity.
55+
1. Select **Certificates & secrets** then **New client secret** to create an application password that your client app can use to prove its identity.
4456

4557
[![Create a new client secret](media/time-series-insights-aad-registration/active-directory-application-keys-save.png)](media/time-series-insights-aad-registration/active-directory-application-keys-save.png#lightbox)
4658

@@ -57,4 +69,4 @@ ms.date: 12/06/2019
5769

5870
1. Next, specify the kind API permission your app requires. By default, **Delegated permissions** will be highlighted. Choose a permission type then, select **Add permissions**.
5971

60-
[![Specify the kind of API permission your app requires](media/time-series-insights-aad-registration/active-directory-app-permission-grant.png)](media/time-series-insights-aad-registration/active-directory-app-permission-grant.png#lightbox)
72+
[![Specify the kind of API permission your app requires](media/time-series-insights-aad-registration/active-directory-app-permission-grant.png)](media/time-series-insights-aad-registration/active-directory-app-permission-grant.png#lightbox)

0 commit comments

Comments
 (0)