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
@@ -88,7 +88,7 @@ Per **step 3**, separating your application's and your user credentials allows y
88
88
89
89
1. The token can then be passed in the `Authorization` header when the application calls the Time Series Insights API.
90
90
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.
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
+
32
42
1.**Redirect URIs** must match the address supplied by the authentication request:
33
43
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.
36
48
37
49
1. Enable the implicit grant flow by checking **Access tokens** or **ID tokens**.
38
50
39
-
[](media/time-series-insights-aad-registration/active-directory-auth-blade.png#lightbox)
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.
44
56
45
57
[](media/time-series-insights-aad-registration/active-directory-application-keys-save.png#lightbox)
46
58
@@ -57,4 +69,4 @@ ms.date: 12/06/2019
57
69
58
70
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**.
59
71
60
-
[](media/time-series-insights-aad-registration/active-directory-app-permission-grant.png#lightbox)
72
+
[](media/time-series-insights-aad-registration/active-directory-app-permission-grant.png#lightbox)
0 commit comments