Skip to content

Commit 1eb38cc

Browse files
committed
more fixes to titles etc
1 parent d9a5236 commit 1eb38cc

11 files changed

+30
-30
lines changed

articles/active-directory/develop/quickstart-daemon-app-java-acquire-token.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ ConfidentialClientApplication cca =
172172
|---------|---------|
173173
| `CLIENT_SECRET` | Is the client secret created for the application in Azure portal. |
174174
| `CLIENT_ID` | Is the **Application (client) ID** for the application registered in the Azure portal. You can find this value in the app's **Overview** page in the Azure portal. |
175-
| `AUTHORITY` | The STS endpoint for user to authenticate. Usually `https://login.microsoftonline.com/{tenant}` for public cloud, where {tenant} is the name of your tenant or your tenant Id.|
175+
| `AUTHORITY` | The STS endpoint for user to authenticate. Usually `https://login.microsoftonline.com/{tenant}` for public cloud, where {tenant} is the name of your tenant or your tenant ID.|
176176

177177
### Requesting tokens
178178

articles/active-directory/develop/quickstart-daemon-app-python-acquire-token.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ app = msal.ConfidentialClientApplication(
146146
|---------|---------|
147147
| `config["secret"]` | Is the client secret created for the application in Azure portal. |
148148
| `config["client_id"]` | Is the **Application (client) ID** for the application registered in the Azure portal. You can find this value in the app's **Overview** page in the Azure portal. |
149-
| `config["authority"]` | The STS endpoint for user to authenticate. Usually `https://login.microsoftonline.com/{tenant}` for public cloud, where {tenant} is the name of your tenant or your tenant Id.|
149+
| `config["authority"]` | The STS endpoint for user to authenticate. Usually `https://login.microsoftonline.com/{tenant}` for public cloud, where {tenant} is the name of your tenant or your tenant ID.|
150150

151151
For more information, please see the [reference documentation for `ConfidentialClientApplication`](https://msal-python.readthedocs.io/en/latest/#confidentialclientapplication).
152152

articles/active-directory/develop/quickstart-mobile-app-ios-sign-in.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -157,11 +157,11 @@ let msalConfiguration = MSALPublicClientApplicationConfig(clientId: kClientID, r
157157
self.applicationContext = try MSALPublicClientApplication(configuration: msalConfiguration)
158158
```
159159

160-
> |Where: | Description |
161-
> |---------|---------|
162-
> | `clientId` | The Application ID from the application registered in *portal.azure.com* |
163-
> | `authority` | The Microsoft identity platform. In most of cases this will be `https://login.microsoftonline.com/common` |
164-
> | `redirectUri` | The redirect URI of the application. You can pass 'nil' to use the default value, or your custom redirect URI. |
160+
|Where: | Description |
161+
|---------|---------|
162+
| `clientId` | The Application ID from the application registered in *portal.azure.com* |
163+
| `authority` | The Microsoft identity platform. In most of cases this will be `https://login.microsoftonline.com/common` |
164+
| `redirectUri` | The redirect URI of the application. You can pass 'nil' to use the default value, or your custom redirect URI. |
165165

166166
### For iOS only, additional app requirements
167167

@@ -220,9 +220,9 @@ let parameters = MSALInteractiveTokenParameters(scopes: kScopes, webviewParamete
220220
self.applicationContext!.acquireToken(with: parameters) { (result, error) in /* Add your handling logic */}
221221
```
222222

223-
> |Where:| Description |
224-
> |---------|---------|
225-
> | `scopes` | Contains the scopes being requested (that is, `[ "user.read" ]` for Microsoft Graph or `[ "<Application ID URL>/scope" ]` for custom web APIs (`api://<Application ID>/access_as_user`)) |
223+
|Where:| Description |
224+
|---------|---------|
225+
| `scopes` | Contains the scopes being requested (that is, `[ "user.read" ]` for Microsoft Graph or `[ "<Application ID URL>/scope" ]` for custom web APIs (`api://<Application ID>/access_as_user`)) |
226226

227227
#### acquireTokenSilent: Get an access token silently
228228

@@ -240,10 +240,10 @@ self.applicationContext!.getCurrentAccount(with: nil) { (currentAccount, previou
240240
}
241241
```
242242

243-
> |Where: | Description |
244-
> |---------|---------|
245-
> | `scopes` | Contains the scopes being requested (that is, `[ "user.read" ]` for Microsoft Graph or `[ "<Application ID URL>/scope" ]` for custom web APIs (`api://<Application ID>/access_as_user`)) |
246-
> | `account` | The account a token is being requested for. This quickstart is about a single account application. If you want to build a multi-account app you'll need to define logic to identify which account to use for token requests using `accountsFromDeviceForParameters:completionBlock:` and passing correct `accountIdentifier` |
243+
|Where: | Description |
244+
|---------|---------|
245+
| `scopes` | Contains the scopes being requested (that is, `[ "user.read" ]` for Microsoft Graph or `[ "<Application ID URL>/scope" ]` for custom web APIs (`api://<Application ID>/access_as_user`)) |
246+
| `account` | The account a token is being requested for. This quickstart is about a single account application. If you want to build a multi-account app you'll need to define logic to identify which account to use for token requests using `accountsFromDeviceForParameters:completionBlock:` and passing correct `accountIdentifier` |
247247

248248
[!INCLUDE [Help and support](includes/error-handling-and-tips/help-support-include.md)]
249249

articles/active-directory/develop/quickstart-single-page-app-angular-sign-in.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Quickstart: Sign in users in single-page apps (SPA) via the authorization code flow with Proof Key for Code Exchange (PKCE) using Angular"
2+
title: "Quickstart: Sign in users in a single-page app (SPA) and call the Microsoft Graph API using Angular"
33
description: In this quickstart, learn how a JavaScript Angular single-page application (SPA) can sign in users of personal accounts, work accounts, and school accounts by using the authorization code flow and call Microsoft Graph.
44
services: active-directory
55
author: henrymbuguakiarie
@@ -15,7 +15,7 @@ ms.custom: aaddev, "scenarios:getting-started", "languages:JavaScript", devx-tra
1515
#Customer intent: As an app developer, I want to learn how to get access tokens and refresh tokens by using the Microsoft identity platform so that my JavaScript Angular app can sign in users of personal accounts, work accounts, and school accounts.
1616
---
1717

18-
# Quickstart: Sign in users in single-page apps (SPA) via the authorization code flow with Proof Key for Code Exchange (PKCE) using Angular
18+
# Quickstart: Sign in users in a single-page app (SPA) and call the Microsoft Graph API using Angular
1919

2020
In this quickstart, you download and run a code sample that demonstrates how a JavaScript Angular single-page application (SPA) can sign in users and call Microsoft Graph using the authorization code flow. The code sample demonstrates how to get an access token to call the Microsoft Graph API or any web API.
2121

articles/active-directory/develop/quickstart-single-page-app-javascript-sign-in.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Quickstart - Sign in users in single-page apps (SPA) via the authorization code flow with Proof Key for Code Exchange (PKCE) using JavaScript
2+
title: "Quickstart: Sign in users in a single-page app (SPA) and call the Microsoft Graph API using JavaScript"
33
description: In this quickstart, learn how a JavaScript single-page application (SPA) can sign in users of personal accounts, work accounts, and school accounts by using the authorization code flow.
44
services: active-directory
55
author: henrymbuguakiarie
@@ -16,7 +16,7 @@ ms.custom: aaddev, "scenarios:getting-started", "languages:JavaScript", devx-tra
1616
#Customer intent: As an app developer, I want to learn how to get access tokens and refresh tokens by using the Microsoft identity platform so that my JavaScript app can sign in users of personal accounts, work accounts, and school accounts.
1717
---
1818

19-
# Quickstart: Sign in users in single-page apps (SPA) via the authorization code flow with Proof Key for Code Exchange (PKCE) using JavaScript
19+
# Quickstart: Sign in users in a single-page app (SPA) and call the Microsoft Graph API using JavaScript
2020

2121
In this quickstart, you download and run a code sample that demonstrates how a JavaScript single-page application (SPA) can sign in users and call Microsoft Graph using the authorization code flow with Proof Key for Code Exchange (PKCE). The code sample demonstrates how to get an access token to call the Microsoft Graph API or any web API.
2222

articles/active-directory/develop/quickstart-single-page-app-react-sign-in.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Quickstart: Sign in users in single-page apps (SPA) via the authorization code flow with Proof Key for Code Exchange (PKCE) using React"
2+
title: "Quickstart: Sign in users in a single-page app (SPA) and call the Microsoft Graph API using React"
33
description: In this quickstart, learn how a JavaScript React single-page application (SPA) can sign in users of personal accounts, work accounts, and school accounts by using the authorization code flow and call Microsoft Graph.
44
services: active-directory
55
author: henrymbuguakiarie
@@ -16,7 +16,7 @@ ms.custom: aaddev, "scenarios:getting-started", "languages:JavaScript", devx-tra
1616
#Customer intent: As an app developer, I want to learn how to login, logout, conditionally render components to authenticated users, and acquire an access token for a protected resource such as Microsoft Graph by using the Microsoft identity platform so that my JavaScript React app can sign in users of personal accounts, work accounts, and school accounts.
1717
---
1818

19-
# Quickstart: Sign in users in single-page apps (SPA) via the authorization code flow with Proof Key for Code Exchange (PKCE) using React
19+
# Quickstart: Sign in users in a single-page app (SPA) and call the Microsoft Graph API using React
2020

2121

2222
In this quickstart, you download and run a code sample that demonstrates how a JavaScript React single-page application (SPA) can sign in users and call Microsoft Graph using the authorization code flow. The code sample demonstrates how to get an access token to call the Microsoft Graph API or any web API.

articles/active-directory/develop/quickstart-web-app-aspnet-core-sign-in.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Quickstart: Add sign-in with Microsoft to an ASP.NET Core web app"
2+
title: "Quickstart: Sign in users and call the Microsoft Graph API from an ASP.NET Core web app"
33
description: Learn how an ASP.NET Core web app leverages Microsoft.Identity.Web to implement Microsoft sign-in using OpenID Connect and call Microsoft Graph
44
services: active-directory
55
author: cilwerner
@@ -18,7 +18,7 @@ ms.custom: "devx-track-csharp, aaddev, identityplatformtop40, scenarios:getting-
1818
#Customer intent: As an application developer, I want to know how to write an ASP.NET Core web app that can sign in personal Microsoft accounts and work/school accounts from any Azure Active Directory instance, then access their data in Microsoft Graph on their behalf.
1919
---
2020

21-
# Quickstart: Add sign-in with Microsoft to an ASP.NET Core web app
21+
# Quickstart: Sign in users and call the Microsoft Graph API from an ASP.NET Core web app
2222

2323
The following quickstart uses a ASP.NET Core web app code sample to demonstrate how to sign in users from any Azure Active Directory (Azure AD) organization.
2424

articles/active-directory/develop/quickstart-web-app-aspnet-sign-in.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Quickstart: Add sign-in with Microsoft to an ASP.NET web app"
2+
title: "Quickstart: Sign in users and call the Microsoft Graph API from an ASP.NET web app"
33
description: Download and run a code sample that shows how an ASP.NET web app can sign in Azure AD users.
44
services: active-directory
55
author: cilwerner
@@ -16,7 +16,7 @@ ms.custom: "devx-track-csharp, aaddev, identityplatformtop40, scenarios:getting-
1616
# Customer intent: As an application developer, I want to see a sample ASP.NET web app that can sign in Azure AD users.
1717
---
1818

19-
# Quickstart: Add sign-in with Microsoft to an ASP.NET web app
19+
# Quickstart: Sign in users and call the Microsoft Graph API from an ASP.NET web app
2020

2121
In this quickstart, you download and run a code sample that demonstrates an ASP.NET web application that can sign in users with Azure Active Directory (Azure AD) accounts.
2222

articles/active-directory/develop/quickstart-web-app-java-sign-in.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Quickstart: Add sign-in with Microsoft to a Java web app"
2+
title: "Quickstart: Sign in users and call the Microsoft Graph API from a Java web app"
33
description: In this quickstart, you'll learn how to add sign-in with Microsoft to a Java web application by using OpenID Connect.
44
services: active-directory
55
author: cilwerner
@@ -13,7 +13,7 @@ ms.author: cwerner
1313
ms.custom: aaddev, scenarios:getting-started, languages:Java, devx-track-java
1414
---
1515

16-
# Quickstart: Add sign-in with Microsoft to a Java web app
16+
# Quickstart: Sign in users and call the Microsoft Graph API from a Java web app
1717

1818
In this quickstart, you download and run a code sample that demonstrates how a Java web application can sign in users and call the Microsoft Graph API. Users from any Azure Active Directory (Azure AD) organization can sign in to the application.
1919

articles/active-directory/develop/quickstart-web-app-nodejs-msal-sign-in.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Quickstart: Add authentication to a Node.js web app with MSAL Node"
2+
title: "Quickstart: Sign in users and call the Microsoft Graph API from a Node.js web application using MSAL Node"
33
description: In this quickstart, you learn how to implement authentication with a Node.js web app and the Microsoft Authentication Library (MSAL) for Node.js.
44
services: active-directory
55
author: cilwerner
@@ -16,7 +16,7 @@ ms.custom: aaddev, scenarios:getting-started, languages:js, devx-track-js
1616
# Customer intent: As an application developer, I want to know how to set up authentication in a web application built using Node.js and MSAL Node.
1717
---
1818

19-
# Quickstart: Add authentication to a Node.js web app with MSAL Node
19+
# Quickstart: Sign in users and call the Microsoft Graph API from a Node.js web application using MSAL Node
2020

2121
In this quickstart, you download and run a code sample that demonstrates how a Node.js web app can sign in users by using the authorization code flow. The code sample also demonstrates how to get an access token to call the Microsoft Graph API.
2222

0 commit comments

Comments
 (0)