Skip to content

Commit 15bb18d

Browse files
author
Ankita Dutta
committed
2 parents 2a6a437 + b74ab03 commit 15bb18d

File tree

3,127 files changed

+21113
-16112
lines changed

Some content is hidden

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

3,127 files changed

+21113
-16112
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: 45 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",

.openpublishing.redirection.azure-monitor.json

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,16 @@
3535
"redirect_url": "/azure/azure-monitor/change/change-analysis",
3636
"redirect_document_id": false
3737
},
38+
{
39+
"source_path_from_root": "/articles/azure-monitor/app/javascript.md",
40+
"redirect_url": "/azure/azure-monitor/app/javascript-sdk",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path_from_root": "/articles/azure-monitor/app/source-map-support.md",
45+
"redirect_url": "/azure/azure-monitor/app/javascript-sdk-advanced",
46+
"redirect_document_id": false
47+
},
3848
{
3949
"source_path_from_root": "/articles/azure-monitor/app/release-notes.md",
4050
"redirect_url": "/azure/azure-monitor/app/app-insights-overview",
@@ -45,6 +55,16 @@
4555
"redirect_url": "/previous-versions/azure/azure-monitor/app/resource-manager-web-app",
4656
"redirect_document_id": false
4757
},
58+
{
59+
"source_path_from_root": "/articles/azure-monitor/app/devops.md",
60+
"redirect_url": "/previous-versions/azure/azure-monitor/app/old-overview",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path_from_root": "/articles/azure-monitor/app/automate-custom-reports.md",
65+
"redirect_url": "/previous-versions/azure/azure-monitor/app/custom-reports",
66+
"redirect_document_id": false
67+
},
4868
{
4969
"source_path_from_root": "/articles/azure-monitor/app/resource-manager-function-app.md",
5070
"redirect_url": "/previous-versions/azure/azure-monitor/app/resource-manager-function-app",
@@ -6025,6 +6045,52 @@
60256045
"source_path_from_root": "/articles/azure-monitor/app/status-monitor-v2-api-reference.md",
60266046
"redirect_url": "/azure/azure-monitor/app/application-insights-asp-net-agent",
60276047
"redirect_document_id": false
6048+
},
6049+
{
6050+
"source_path_from_root": "/articles/azure-monitor/app/data-model.md",
6051+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6052+
"redirect_document_id": false
6053+
},
6054+
{
6055+
"source_path_from_root": "/articles/azure-monitor/app/data-model-request-telemetry.md",
6056+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6057+
"redirect_document_id": false
6058+
},
6059+
{
6060+
"source_path_from_root": "/articles/azure-monitor/app/data-model-dependency-telemetry.md",
6061+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6062+
"redirect_document_id": false
6063+
},
6064+
{
6065+
"source_path_from_root": "/articles/azure-monitor/app/data-model-exception-telemetry.md",
6066+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6067+
"redirect_document_id": false
6068+
},
6069+
{
6070+
"source_path_from_root": "/articles/azure-monitor/app/data-model-trace-telemetry.md",
6071+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6072+
"redirect_document_id": false
6073+
},
6074+
{
6075+
"source_path_from_root": "/articles/azure-monitor/app/data-model-event-telemetry.md",
6076+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6077+
"redirect_document_id": false
6078+
},
6079+
{
6080+
"source_path_from_root": "/articles/azure-monitor/app/data-model-metric-telemetry.md",
6081+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6082+
"redirect_document_id": false
6083+
},
6084+
{
6085+
"source_path_from_root": "/articles/azure-monitor/app/data-model-pageview-telemetry.md",
6086+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6087+
"redirect_document_id": false
6088+
},
6089+
{
6090+
"source_path_from_root": "/articles/azure-monitor/app/data-model-context.md",
6091+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6092+
"redirect_document_id": false
60286093
}
6094+
60296095
]
60306096
}

.openpublishing.redirection.json

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13764,6 +13764,31 @@
1376413764
"redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
1376513765
"redirect_document_id": ""
1376613766
},
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+
},
1376713792
{
1376813793
"source_path_from_root": "/articles/search/cognitive-search-tutorial-aml-designer-custom-skill.md",
1376913794
"redirect_url": "/previous-versions/azure/search/cognitive-search-tutorial-aml-designer-custom-skill",
@@ -22415,6 +22440,11 @@
2241522440
"source_path": "articles/private-multi-access-edge-compute-mec/metaswitch-fusion-core-overview.md",
2241622441
"redirect_URL": "/azure/private-5g-core",
2241722442
"redirect_document_id": false
22443+
},
22444+
{
22445+
"source_path": "articles/communications-gateway/rotate-secrets.md",
22446+
"redirect_URL": "/azure/communications-gateway/whats-new",
22447+
"redirect_document_id": false
2241822448
}
2241922449
]
2242022450
}

articles/active-directory-b2c/custom-policies-series-call-rest-api.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 01/30/2023
13+
ms.date: 03/16/2023
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: B2C
@@ -104,7 +104,7 @@ You need to deploy an app, which will serve as your external app. Your custom po
104104

105105
1. To test the app works as expected, use the following steps:
106106
1. In your terminal, run the `node index.js` command to start your app server.
107-
1. To make a POST request similar to the one shown below, you can use an HTTP client such as [Microsoft PowerShell](https://learn.microsoft.com/powershell/scripting/overview) or [Postman](https://www.postman.com/):
107+
1. To make a POST request similar to the one shown below, you can use an HTTP client such as [Microsoft PowerShell](/powershell/scripting/overview) or [Postman](https://www.postman.com/):
108108

109109
```http
110110
POST http://localhost/validate-accesscode HTTP/1.1
@@ -150,7 +150,7 @@ Follow the steps in [Deploy your app to Azure](../app-service/quickstart-nodejs.
150150
151151
- Service endpoint looks similar to `https://custompolicyapi.azurewebsites.net/validate-accesscode`.
152152
153-
You can test the app you've deployed by using an HTTP client such as [Microsoft PowerShell](https://learn.microsoft.com/powershell/scripting/overview) or [Postman](https://www.postman.com/). This time, use `https://custompolicyapi.azurewebsites.net/validate-accesscode` URL as the endpoint.
153+
You can test the app you've deployed by using an HTTP client such as [Microsoft PowerShell](/powershell/scripting/overview) or [Postman](https://www.postman.com/). This time, use `https://custompolicyapi.azurewebsites.net/validate-accesscode` URL as the endpoint.
154154

155155
## Step 2 - Call the REST API
156156

@@ -302,6 +302,12 @@ Then, update the *Metadata*, *InputClaimsTransformations*, and *InputClaims* of
302302
</InputClaims>
303303
```
304304

305+
## Receive data from REST API
306+
307+
If your REST API returns data, which you want to include as claims in your policy, you can receive it by specifying claims in the `OutputClaims` element of the RESTful technical profile. If the name of the claim defined in your policy is different from the name defined in the REST API, you need to map these names by using the `PartnerClaimType` attribute.
308+
309+
Use the steps in [Receiving data](api-connectors-overview.md?pivots=b2c-custom-policy#receiving-data) to learn how to format the data the custom policy expects, how to handle nulls values, and how to parse REST the API's nested JSON body.
310+
305311
## Next steps
306312
307313
Next, learn:

articles/active-directory-b2c/custom-policies-series-hello-world.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 01/30/2023
13+
ms.date: 03/16/2023
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: B2C
@@ -59,7 +59,7 @@ If you haven't already done so, create the following encryption keys. To automat
5959

6060
<BuildingBlocks>
6161
<!-- Building Blocks Here-->
62-
<BuildingBlocks>
62+
</BuildingBlocks>
6363

6464
<ClaimsProviders>
6565
<!-- Claims Providers Here-->
@@ -280,7 +280,7 @@ After the policy finishes execution, you're redirected to `https://jwt.ms`, and
280280
}.[Signature]
281281
```
282282

283-
Notice the `message` and `sub` claims, which we set as output claims](relyingparty.md#outputclaims) in the `RelyingParty` section.
283+
Notice the `message` and `sub` claims, which we set as [output claims](relyingparty.md#outputclaims) in the `RelyingParty` section.
284284

285285
## Next steps
286286

@@ -303,4 +303,4 @@ Next, learn:
303303

304304
- About custom policy [claims data type](claimsschema.md#datatype).
305305

306-
- About custom policy [user input types](claimsschema.md#userinputtype).
306+
- About custom policy [user input types](claimsschema.md#userinputtype).

articles/active-directory-b2c/custom-policies-series-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In Azure Active Directory B2C (Azure AD B2C), you can create user experiences by
2222

2323
User flows are already customizable such as [changing UI](customize-ui.md), [customizing language](language-customization.md) and using [custom attributes](user-flow-custom-attributes.md). However, these customizations might not cover all your business specific needs, which is the reason why you need custom policies.
2424

25-
While you can use pre-made [custom policy starter pack](/azure/active-directory-b2c/tutorial-create-user-flows?pivots=b2c-custom-policy#custom-policy-starter-pack), it's important for you understand how custom policy is built from scratch. In this how-to guide series, you'll learn what you need to understand for you to customize the behavior of your user experience by using custom policies. At the end of this how-to guide series, you should be able to read and understand existing custom policies or write your own from scratch.
25+
While you can use pre-made [custom policy starter pack](./tutorial-create-user-flows.md?pivots=b2c-custom-policy#custom-policy-starter-pack), it's important for you understand how custom policy is built from scratch. In this how-to guide series, you'll learn what you need to understand for you to customize the behavior of your user experience by using custom policies. At the end of this how-to guide series, you should be able to read and understand existing custom policies or write your own from scratch.
2626

2727
## Prerequisites
2828

@@ -48,4 +48,4 @@ This how-to guide series consists of multiple articles. We recommend that you st
4848

4949
- Learn about [Azure AD B2C TrustFrameworkPolicy BuildingBlocks](buildingblocks.md)
5050

51-
- [Write your first Azure Active Directory B2C custom policy - Hello World!](custom-policies-series-hello-world.md)
51+
- [Write your first Azure Active Directory B2C custom policy - Hello World!](custom-policies-series-hello-world.md)

articles/active-directory-b2c/data-residency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ The following locations are in the process of being added to the list. For now,
5959
## EU Data Boundary
6060

6161
> [!IMPORTANT]
62-
> For comprehensive details about Microsoft's EU Data Boundary commitment, see [Microsoft's EU Data Boundary documentation](https://learn.microsoft.com/privacy/eudb/eu-data-boundary-learn).
62+
> For comprehensive details about Microsoft's EU Data Boundary commitment, see [Microsoft's EU Data Boundary documentation](/privacy/eudb/eu-data-boundary-learn).
6363
6464
## Remote profile solution
6565

0 commit comments

Comments
 (0)