Skip to content

Commit 2081faa

Browse files
pauljewellmsftpauljewellmsft
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into pauljewell-get-endpoint-srp
2 parents aa81c17 + c0b63ea commit 2081faa

File tree

659 files changed

+31595
-26806
lines changed

Some content is hidden

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

659 files changed

+31595
-26806
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.azure-monitor.json

Lines changed: 47 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,6 @@
11
{
22
"redirections": [
3-
{
4-
"source_path_from_root": "/articles/azure-monitor/snapshot-debugger/snapshot-debugger-troubleshoot.md",
5-
"redirect_url": "https://learn.microsoft.com/troubleshoot/azure/azure-monitor/app-insights/snapshot-debugger-troubleshoot",
6-
"redirect_document_id": false
7-
},
8-
{
3+
{
94
"source_path_from_root": "/articles/azure-monitor/best-practices.md",
105
"redirect_url": "/azure/azure-monitor/getting-started",
116
"redirect_document_id": false
@@ -6045,6 +6040,52 @@
60456040
"source_path_from_root": "/articles/azure-monitor/app/status-monitor-v2-api-reference.md",
60466041
"redirect_url": "/azure/azure-monitor/app/application-insights-asp-net-agent",
60476042
"redirect_document_id": false
6043+
},
6044+
{
6045+
"source_path_from_root": "/articles/azure-monitor/app/data-model.md",
6046+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6047+
"redirect_document_id": false
6048+
},
6049+
{
6050+
"source_path_from_root": "/articles/azure-monitor/app/data-model-request-telemetry.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-dependency-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-exception-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-trace-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-event-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-metric-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-pageview-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-context.md",
6086+
"redirect_url": "/azure/azure-monitor/app/data-model-complete",
6087+
"redirect_document_id": false
60486088
}
6089+
60496090
]
60506091
}

‎.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.json

Lines changed: 22461 additions & 22445 deletions
Large diffs are not rendered by default.

‎articles/active-directory-b2c/faq.yml

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ metadata:
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: faq
12-
ms.date: 02/09/2023
12+
ms.date: 03/15/2023
1313
ms.author: godonnell
1414
ms.subservice: B2C
1515
ms.custom: "b2c-support"
@@ -64,7 +64,12 @@ sections:
6464
* Microsoft account: openid email profile
6565
* Amazon: profile
6666
* LinkedIn: r_emailaddress, r_basicprofile
67-
67+
68+
- question: |
69+
I'm using ADFS as an identity provider in Azure AD B2C. When I try to initiate a sign out request from Azure AD B2C, ADFS shows the error *MSIS7084: SAML logout request and logout response messages must be signed when using SAML HTTP Redirect or HTTP POST binding*. How do I resolve this issue?
70+
answer: |
71+
On the ADFS server, run: `Set-AdfsProperties -SignedSamlRequestsRequired $true`. This will force Azure AD B2C to sign all requests to ADFS.
72+
6873
- question: |
6974
Does my application have to be run on Azure for it work with Azure AD B2C?
7075
answer: |
@@ -256,6 +261,11 @@ sections:
256261
257262
1. Retrieve the `RefreshToken` again.
258263
264+
- question: |
265+
I use multiple tabs in a web browser to sign in to multiple applications that I registered in the same Azure AD B2C tenant. When I try to perform a single sign out, not all of the applications are signed out. Why does this happen?
266+
answer: |
267+
Currently, Azure AD B2C doesn't support single sign out for this specific scenario. It's caused by cookie contention as all the applications operates on the same cookie simultaneously.
268+
259269
- question: |
260270
How do I report issues with Azure AD B2C?
261271
answer: |

‎articles/active-directory-b2c/identity-provider-generic-openid-connect.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,7 @@ Define the OpenId Connect identity provider by adding it to the **ClaimsProvider
8181
<OutputClaim ClaimTypeReferenceId="email" PartnerClaimType="email" />
8282
<OutputClaim ClaimTypeReferenceId="authenticationSource" DefaultValue="socialIdpAuthentication" AlwaysUseDefaultValue="true" />
8383
<OutputClaim ClaimTypeReferenceId="identityProvider" PartnerClaimType="iss" />
84+
<OutputClaim ClaimTypeReferenceId="objectId" PartnerClaimType="oid"/>
8485
</OutputClaims>
8586
<OutputClaimsTransformations>
8687
<OutputClaimsTransformation ReferenceId="CreateRandomUPNUserName"/>

0 commit comments

Comments
 (0)