Skip to content

Commit 1ac615b

Browse files
Merge branch 'main' into rsarkar/call-recording-byos
2 parents 2ffe6b1 + d34558a commit 1ac615b

File tree

2,719 files changed

+15738
-12947
lines changed

Some content is hidden

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

2,719 files changed

+15738
-12947
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: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,16 @@
5555
"redirect_url": "/previous-versions/azure/azure-monitor/app/resource-manager-web-app",
5656
"redirect_document_id": false
5757
},
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+
},
5868
{
5969
"source_path_from_root": "/articles/azure-monitor/app/resource-manager-function-app.md",
6070
"redirect_url": "/previous-versions/azure/azure-monitor/app/resource-manager-function-app",
@@ -6035,6 +6045,52 @@
60356045
"source_path_from_root": "/articles/azure-monitor/app/status-monitor-v2-api-reference.md",
60366046
"redirect_url": "/azure/azure-monitor/app/application-insights-asp-net-agent",
60376047
"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
60386093
}
6094+
60396095
]
60406096
}

.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: 7 additions & 1 deletion
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
@@ -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-domain-services/troubleshoot-alerts.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010
ms.subservice: domain-services
1111
ms.workload: identity
1212
ms.topic: troubleshooting
13-
ms.date: 03/02/2023
13+
ms.date: 03/15/2023
1414
ms.author: justinha
1515

1616
---
@@ -314,6 +314,19 @@ When the managed domain is enabled again, the managed domain's health automatica
314314
315315
[Check the Azure AD DS health](check-health.md) for alerts that indicate problems in the configuration of the managed domain. If you're able to resolve alerts that indicate a configuration issue, wait two hours and check back to see if the synchronization has completed. When ready, [open an Azure support request][azure-support] to re-enable the managed domain.
316316

317+
## AADDS600: Unresolved health alerts for 30 days
318+
319+
### Alert Message
320+
321+
*Microsoft can’t manage the domain controllers for this managed domain due to unresolved health alerts \[IDs\]. This is blocking critical security updates as well as a planned migration to Windows Server 2019 for these domain controllers. Follow steps in the alert to resolve the issue. Failure to resolve this issue within 30 days will result in suspension of the managed domain.*
322+
323+
### Resolution
324+
325+
> [!WARNING]
326+
> If a managed domain is suspended for an extended period of time, there's a danger of it being deleted. Resolve the reason for suspension as quickly as possible. For more information, see [Understand the suspended states for Azure AD DS](suspension.md).
327+
328+
[Check the Azure AD DS health](check-health.md) for alerts that indicate problems in the configuration of the managed domain. If you're able to resolve alerts that indicate a configuration issue, wait six hours and check back to see if the alert is removed. [Open an Azure support request][azure-support] if you need assistance.
329+
317330
## Next steps
318331

319332
If you still have issues, [open an Azure support request][azure-support] for additional troubleshooting assistance.

articles/active-directory/app-provisioning/application-provisioning-config-problem-scim-compatibility.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Known issues with System for Cross-Domain Identity Management (SCIM) 2.0 protocol compliance - Azure AD
2+
title: Known issues with System for Cross-Domain Identity Management (SCIM) 2.0 protocol compliance
33
description: How to solve common protocol compatibility issues faced when adding a non-gallery application that supports SCIM 2.0 to Azure AD
44
services: active-directory
55
author: kenwith

articles/active-directory/app-provisioning/on-premises-application-provisioning-architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'Azure AD on-premises application provisioning architecture | Microsoft Docs'
2+
title: 'Azure AD on-premises application provisioning architecture'
33
description: Presents an overview of on-premises application provisioning architecture.
44
services: active-directory
55
author: billmath

articles/active-directory/app-provisioning/on-premises-scim-provisioning.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,3 +64,4 @@ The following video provides an overview of on-premises provisoning.
6464
- [App provisioning](user-provisioning.md)
6565
- [Generic SQL connector](on-premises-sql-connector-configure.md)
6666
- [Tutorial: ECMA Connector Host generic SQL connector](tutorial-ecma-sql-connector.md)
67+
- [Known issues](known-issues.md)

0 commit comments

Comments
 (0)