Skip to content

Commit 1f2e2c2

Browse files
authored
Merge branch 'main' into kaveesh/ama_windows
2 parents 2d008f1 + 6e85608 commit 1f2e2c2

File tree

7,096 files changed

+98780
-64506
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

7,096 files changed

+98780
-64506
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -760,7 +760,7 @@
760760
},
761761
{
762762
"path_to_root": "azure-spring-apps-reference-architecture",
763-
"url": "https://github.com/Azure/azure-spring-apps-reference-architecture",
763+
"url": "https://github.com/Azure/azure-spring-apps-landing-zone-accelerator",
764764
"branch": "reference-architecture",
765765
"branch_mapping": {}
766766
},

.openpublishing.redirection.active-directory.json

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -95,6 +95,11 @@
9595
"redirect_url": "/graph/tutorial-lifecycle-workflows-onboard-custom-workflow",
9696
"redirect_document_id": false
9797
},
98+
{
99+
"source_path_from_root": "/articles/active-directory/governance/manage-lifecycle-workflows.md",
100+
"redirect_url": "/azure/active-directory/governance/understanding-lifecycle-workflows",
101+
"redirect_document_id": false
102+
},
98103
{
99104
"source_path_from_root": "/articles/active-directory/governance/lifecycle-workflows-developer-reference.md",
100105
"redirect_url": "/graph/api/resources/identitygovernance-workflow",
@@ -160,6 +165,46 @@
160165
"redirect_url": "/azure/active-directory/develop/workload-identity-federation-create-trust",
161166
"redirect_document_id": false
162167
},
168+
{
169+
"source_path_from_root": "/articles/active-directory/develop/workload-identities-overview.md",
170+
"redirect_url": "/azure/active-directory/workload-identities/workload-identities-overview",
171+
"redirect_document_id": false
172+
},
173+
{
174+
"source_path_from_root": "/articles/active-directory/develop/workload-identities-faqs.md",
175+
"redirect_url": "/azure/active-directory/workload-identities/workload-identities-faqs",
176+
"redirect_document_id": false
177+
},
178+
{
179+
"source_path_from_root": "/articles/active-directory/develop/workload-identity-federation.md",
180+
"redirect_url": "/azure/active-directory/workload-identities/workload-identity-federation",
181+
"redirect_document_id": false
182+
},
183+
{
184+
"source_path_from_root": "/articles/active-directory/develop/workload-identity-federation-create-trust.md",
185+
"redirect_url": "/azure/active-directory/workload-identities/workload-identity-federation-create-trust",
186+
"redirect_document_id": false
187+
},
188+
{
189+
"source_path_from_root": "/articles/active-directory/develop/workload-identity-federation-create-trust-user-assigned-managed-identity.md",
190+
"redirect_url": "/azure/active-directory/workload-identities/workload-identity-federation-create-trust-user-assigned-managed-identity",
191+
"redirect_document_id": false
192+
},
193+
{
194+
"source_path_from_root": "/articles/active-directory/develop/workload-identity-federation-create-trust-gcp.md",
195+
"redirect_url": "/azure/active-directory/workload-identities/workload-identity-federation-create-trust-gcp",
196+
"redirect_document_id": false
197+
},
198+
{
199+
"source_path_from_root": "/articles/active-directory/develop/workload-identity-federation-block-using-azure-policy.md",
200+
"redirect_url": "/azure/active-directory/workload-identities/workload-identity-federation-block-using-azure-policy",
201+
"redirect_document_id": false
202+
},
203+
{
204+
"source_path_from_root": "/articles/active-directory/develop/workload-identity-federation-considerations.md",
205+
"redirect_url": "/azure/active-directory/workload-identities/workload-identity-federation-considerations",
206+
"redirect_document_id": false
207+
},
163208
{
164209
"source_path_from_root": "/articles/active-directory/develop/active-directory-v2-limitations.md",
165210
"redirect_url": "/azure/active-directory/develop/v2-overview",
@@ -10941,6 +10986,11 @@
1094110986
"redirect_url": "/azure/active-directory-b2c/tenant-management-add-administrator",
1094210987
"redirect_document_id": false
1094310988
},
10989+
{
10990+
"source_path_from_root": "/articles/active-directory-b2c/support-options.md",
10991+
"redirect_url": "/azure/active-directory-b2c/find-help-open-support-ticket",
10992+
"redirect_document_id": false
10993+
},
1094410994
{
1094510995
"source_path": "articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-arm.md",
1094610996
"redirect_url": "/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-arm",

.openpublishing.redirection.azure-monitor.json

Lines changed: 310 additions & 10 deletions
Large diffs are not rendered by default.

.openpublishing.redirection.azure-productivity.json

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,61 @@
8989
"source_path": "articles/lab-services/troubleshoot.md",
9090
"redirect_url": "/azure/lab-services/troubleshoot-lab-creation",
9191
"redirect_document_id": true
92+
},
93+
{
94+
"source_path": "articles/lab-services/quick-create-lab-portal.md",
95+
"redirect_url": "/azure/lab-services/quick-create-connect-lab",
96+
"redirect_document_id": true
97+
},
98+
{
99+
"source_path": "articles/lab-services/tutorial-setup-lab-plan.md",
100+
"redirect_url": "/azure/lab-services/quick-create-resources",
101+
"redirect_document_id": true
102+
},
103+
{
104+
"source_path": "articles/lab-services/quick-create-lab-plan-portal.md",
105+
"redirect_url": "/azure/lab-services/quick-create-resources",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path": "articles/lab-services/quick-create-lab-bicep.md",
110+
"redirect_url": "/azure/lab-services/how-to-create-lab-bicep",
111+
"redirect_document_id": true
112+
},
113+
{
114+
"source_path": "articles/lab-services/quick-create-lab-plan-bicep.md",
115+
"redirect_url": "/azure/lab-services/how-to-create-lab-plan-bicep",
116+
"redirect_document_id": true
117+
},
118+
{
119+
"source_path": "articles/lab-services/quick-create-lab-plan-powershell.md",
120+
"redirect_url": "/azure/lab-services/how-to-create-lab-plan-powershell",
121+
"redirect_document_id": true
122+
},
123+
{
124+
"source_path": "articles/lab-services/quick-create-lab-plan-python.md",
125+
"redirect_url": "/azure/lab-services/how-to-create-lab-plan-python",
126+
"redirect_document_id": true
127+
},
128+
{
129+
"source_path": "articles/lab-services/quick-create-lab-plan-template.md",
130+
"redirect_url": "/azure/lab-services/how-to-create-lab-plan-template",
131+
"redirect_document_id": true
132+
},
133+
{
134+
"source_path": "articles/lab-services/quick-create-lab-powershell.md",
135+
"redirect_url": "/azure/lab-services/how-to-create-lab-powershell",
136+
"redirect_document_id": true
137+
},
138+
{
139+
"source_path": "articles/lab-services/quick-create-lab-python.md",
140+
"redirect_url": "/azure/lab-services/how-to-create-lab-python",
141+
"redirect_document_id": true
142+
},
143+
{
144+
"source_path": "articles/lab-services/quick-create-lab-template.md",
145+
"redirect_url": "/azure/lab-services/how-to-create-lab-template",
146+
"redirect_document_id": true
92147
}
93148
]
94149
}

.openpublishing.redirection.defender-for-cloud.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -787,7 +787,7 @@
787787
},
788788
{
789789
"source_path_from_root": "/articles/defender-for-cloud/os-coverage.md",
790-
"redirect_url": "/azure/defender-for-cloud/monitoring-components",
790+
"redirect_url": "/azure/defender-for-cloud/support-matrix-defender-for-cloud#supported-operating-systems",
791791
"redirect_document_id": false
792792
},
793793
{

.openpublishing.redirection.deployment-environments.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,11 @@
1414
"source_path_from_root": "/articles/deployment-environments/tutorial-create-and-configure-projects.md",
1515
"redirect_url": "/azure/deployment-environments/quickstart-create-and-configure-projects",
1616
"redirect_document_id": false
17+
},
18+
{
19+
"source_path_from_root": "/articles/deployment-environments/how-to-configure-use-cli.md",
20+
"redirect_url": "https://aka.ms/CLI-reference",
21+
"redirect_document_id": false
1722
}
1823
]
1924
}

.openpublishing.redirection.dev-box.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,11 @@
99
"source_path_from_root": "/articles/dev-box/quickstart-configure-dev-box-project.md",
1010
"redirect_url": "/azure/dev-box/quickstart-configure-dev-box-service",
1111
"redirect_document_id": false
12+
},
13+
{
14+
"source_path_from_root": "/articles/dev-box/cli-reference-subset.md",
15+
"redirect_url": "https://aka.ms/CLI-reference",
16+
"redirect_document_id": false
1217
}
1318
]
1419
}

.openpublishing.redirection.healthcare-apis.json

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -665,13 +665,17 @@
665665
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-mapping-debugger",
666666
"redirect_document_id": false
667667
},
668+
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-monitoring-tab.md",
669+
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs",
670+
"redirect_document_id": false
671+
},
668672
{ "source_path_from_root": "/articles/healthcare-apis/events/events-display-metrics.md",
669673
"redirect_url": "/azure/healthcare-apis/events/events-use-metrics",
670674
"redirect_document_id": false
671675
},
672676
{ "source_path_from_root": "/articles/healthcare-apis/events/events-export-logs-metrics.md",
673677
"redirect_url": "/azure/healthcare-apis/events/events-enable-diagnostic-settings",
674-
"redirect_document_id": true
678+
"redirect_document_id": false
675679
}
676680
]
677681
}

.openpublishing.redirection.json

Lines changed: 51 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/databox-online/azure-stack-edge-zero-touch-provisioning.md",
5+
"redirect_url": "/azure/databox-online/azure-stack-edge-powershell-based-configuration",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "articles/azure-video-analyzer/video-analyzer-docs/access-policies.md",
510
"redirect_url": "/previous-versions/azure/azure-video-analyzer/video-analyzer-docs/access-policies",
@@ -13759,6 +13764,31 @@
1375913764
"redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
1376013765
"redirect_document_id": ""
1376113766
},
13767+
{
13768+
"source_path_from_root": "/articles/search/tutorial-csharp-create-first-app.md",
13769+
"redirect_url": "/previous-versions/azure/search/tutorial-csharp-create-first-app",
13770+
"redirect_document_id": false
13771+
},
13772+
{
13773+
"source_path_from_root": "/articles/search/tutorial-csharp-paging.md",
13774+
"redirect_url": "/previous-versions/azure/search/tutorial-csharp-paging",
13775+
"redirect_document_id": false
13776+
},
13777+
{
13778+
"source_path_from_root": "/articles/search/tutorial-csharp-type-ahead-and-suggestions.md",
13779+
"redirect_url": "/previous-versions/azure/search/tutorial-csharp-type-ahead-and-suggestions",
13780+
"redirect_document_id": false
13781+
},
13782+
{
13783+
"source_path_from_root": "/articles/search/tutorial-csharp-facets.md",
13784+
"redirect_url": "/previous-versions/azure/search/tutorial-csharp-facets",
13785+
"redirect_document_id": false
13786+
},
13787+
{
13788+
"source_path_from_root": "/articles/search/tutorial-csharp-orders.md",
13789+
"redirect_url": "/previous-versions/azure/search/tutorial-csharp-orders",
13790+
"redirect_document_id": false
13791+
},
1376213792
{
1376313793
"source_path_from_root": "/articles/search/cognitive-search-tutorial-aml-designer-custom-skill.md",
1376413794
"redirect_url": "/previous-versions/azure/search/cognitive-search-tutorial-aml-designer-custom-skill",
@@ -22306,6 +22336,11 @@
2230622336
"redirect_url": "/azure/azure-arc/servers/onboard-group-policy-powershell",
2230722337
"redirect_document_id": "false"
2230822338
},
22339+
{
22340+
"source_path_from_root": "/articles/azure-arc/kubernetes/plan-at-scale-deployment.md",
22341+
"redirect_url": "/azure/azure-arc/kubernetes/overview",
22342+
"redirect_document_id": "false"
22343+
},
2230922344
{
2231022345
"source_path": "articles/azure-cache-for-redis/redis-cache-insights-overview.md",
2231122346
"redirect_url": "/azure/azure-cache-for-redis/cache-insights-overview",
@@ -22401,11 +22436,26 @@
2240122436
"redirect_url": "/previous-versions/azure/virtual-machines/linux/openshift-container-platform-3x",
2240222437
"redirect_document_id": false
2240322438
},
22404-
22439+
{
22440+
"source_path": "articles/orbital/orbital-preview.md",
22441+
"redirect_url": "/azure/orbital/overview",
22442+
"redirect_document_id": false
22443+
},
2240522444
{
2240622445
"source_path": "articles/private-multi-access-edge-compute-mec/metaswitch-fusion-core-overview.md",
2240722446
"redirect_URL": "/azure/private-5g-core",
2240822447
"redirect_document_id": false
22448+
},
22449+
{
22450+
"source_path": "articles/communications-gateway/rotate-secrets.md",
22451+
"redirect_URL": "/azure/communications-gateway/whats-new",
22452+
"redirect_document_id": false
22453+
},
22454+
{
22455+
"source_path": "articles/batch/high-availability-disaster-recovery.md",
22456+
"redirect_URL": "/azure/reliability/reliability-batch",
22457+
"redirect_document_id": false
2240922458
}
22459+
2241022460
]
2241122461
}

articles/active-directory-b2c/access-tokens.md

Lines changed: 17 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Request an access token - Azure Active Directory B2C
2+
title: Request an access token in Azure Active Directory B2C
33
description: Learn how to request an access token from Azure Active Directory B2C.
44
services: active-directory-b2c
55
author: kengaderdus
@@ -8,20 +8,20 @@ manager: CelesteDG
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 02/07/2022
11+
ms.date: 03/09/2023
1212
ms.custom: project-no-code
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515

1616
---
1717
# Request an access token in Azure Active Directory B2C
1818

19-
An *access token* contains claims that you can use in Azure Active Directory B2C (Azure AD B2C) to identify the granted permissions to your APIs. When calling a resource server, an access token must be present in the HTTP request. An access token is denoted as **access_token** in the responses from Azure AD B2C.
19+
An *access token* contains claims that you can use in Azure Active Directory B2C (Azure AD B2C) to identify the granted permissions to your APIs. To call a resource server, the HTTP request must include an access token. An access token is denoted as **access_token** in the responses from Azure AD B2C.
2020

2121
This article shows you how to request an access token for a web application and web API. For more information about tokens in Azure AD B2C, see the [overview of tokens in Azure Active Directory B2C](tokens-overview.md).
2222

2323
> [!NOTE]
24-
> **Web API chains (On-Behalf-Of) is not supported by Azure AD B2C.** - Many architectures include a web API that needs to call another downstream web API, both secured by Azure AD B2C. This scenario is common in clients that have a web API back end, which in turn calls a another service. This chained web API scenario can be supported by using the OAuth 2.0 JWT Bearer Credential grant, otherwise known as the On-Behalf-Of flow. However, the On-Behalf-Of flow is not currently implemented in Azure AD B2C. Although On-Behalf-Of works for applications registered in Azure AD, it does not work for applications registered in Azure AD B2C, regardless of the tenant (Azure AD or Azure AD B2C) that is issuing the tokens.
24+
> **Web API chains (On-Behalf-Of) is not supported by Azure AD B2C** - Many architectures include a web API that needs to call another downstream web API, both secured by Azure AD B2C. This scenario is common in clients that have a web API back end, which in turn calls a another service. This chained web API scenario can be supported by using the OAuth 2.0 JWT Bearer Credential grant, otherwise known as the On-Behalf-Of flow. However, the On-Behalf-Of flow is not currently implemented in Azure AD B2C. Although On-Behalf-Of works for applications registered in Azure AD, it does not work for applications registered in Azure AD B2C, regardless of the tenant (Azure AD or Azure AD B2C) that is issuing the tokens.
2525
2626
## Prerequisites
2727

@@ -60,17 +60,7 @@ If the **response_type** parameter in an `/authorize` request includes `token`,
6060

6161
## Request a token
6262

63-
To request an access token, you need an authorization code. Below is an example of a request to the `/authorize` endpoint for an authorization code.
64-
65-
In the following example, you replace these values in the query string:
66-
67-
- `<tenant-name>` - The name of your [Azure AD B2C tenant](tenant-management-read-tenant-name.md#get-your-tenant-name). If you're using a custom domain, replace `tenant-name.b2clogin.com` with your domain, such as `contoso.com`.
68-
- `<policy-name>` - The name of your custom policy or user flow.
69-
- `<application-ID>` - The application identifier of the web application that you registered to support the user flow.
70-
- `<application-ID-URI>` - The application identifier URI that you set under **Expose an API** blade of the client application.
71-
- `<scope-name>` - The name of the scope that you added under **Expose an API** blade of the client application.
72-
- `<redirect-uri>` - The **Redirect URI** that you entered when you registered the client application.
73-
63+
To request an access token, you need an authorization code. The following is an example of a request to the `/authorize` endpoint for an authorization code:
7464
```http
7565
GET https://<tenant-name>.b2clogin.com/<tenant-name>.onmicrosoft.com/<policy-name>/oauth2/v2.0/authorize?
7666
client_id=<application-ID>
@@ -80,17 +70,26 @@ client_id=<application-ID>
8070
&response_type=code
8171
```
8272

73+
Replace the values in the query string as follows:
74+
75+
- `<tenant-name>` - The name of your [Azure AD B2C tenant](tenant-management-read-tenant-name.md#get-your-tenant-name). If you're using a custom domain, replace `tenant-name.b2clogin.com` with your domain, such as `contoso.com`.
76+
- `<policy-name>` - The name of your custom policy or user flow.
77+
- `<application-ID>` - The application identifier of the web application that you registered to support the user flow.
78+
- `<application-ID-URI>` - The application identifier URI that you set under **Expose an API** blade of the client application.
79+
- `<scope-name>` - The name of the scope that you added under **Expose an API** blade of the client application.
80+
- `<redirect-uri>` - The **Redirect URI** that you entered when you registered the client application.
81+
8382
To get a feel of how the request works, paste the request into your browser and run it.
8483

85-
This is the interactive part of the flow, where you take action. You're asked to complete the user flow's workflow. This might involve entering your username and password in a sign in form or any other number of steps. The steps you complete depend on how the user flow is defined.
84+
This's the interactive part of the flow, where you take action. You're asked to complete the user flow's workflow. This might involve entering your username and password in a sign in form or any other number of steps. The steps you complete depend on how the user flow is defined.
8685

8786
The response with the authorization code should be similar to this example:
8887

8988
```
9089
https://jwt.ms/?code=eyJraWQiOiJjcGltY29yZV8wOTI1MjAxNSIsInZlciI6IjEuMC...
9190
```
9291

93-
After successfully receiving the authorization code, you can use it to request an access token. Note that the parameters are in the body of the HTTP POST request:
92+
After successfully receiving the authorization code, you can use it to request an access token. The parameters are in the body of the HTTP POST request:
9493

9594
```http
9695
POST <tenant-name>.b2clogin.com/<tenant-name>.onmicrosoft.com/<policy-name>/oauth2/v2.0/token HTTP/1.1
@@ -105,7 +104,7 @@ grant_type=authorization_code
105104
&client_secret=2hMG2-_:y12n10vwH...
106105
```
107106

108-
If you're testing this POST HTTP request, you can use any HTTP client such as [Microsoft PowerShell](/powershell/scripting/overview) or [Postman](https://www.postman.com/).
107+
If you want to test this POST HTTP request, you can use any HTTP client such as [Microsoft PowerShell](/powershell/scripting/overview) or [Postman](https://www.postman.com/).
109108

110109
A successful token response looks like this:
111110

0 commit comments

Comments
 (0)