Skip to content

Commit db7c2ba

Browse files
committed
2 parents 3484f55 + 9d6e521 commit db7c2ba

544 files changed

Lines changed: 8938 additions & 29764 deletions

File tree

Some content is hidden

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

.openpublishing.redirection.json

Lines changed: 215 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,215 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/azure-health-insights/configure-containers.md",
5+
"redirect_url": "/previous-versions/azure/azure-health-insights/configure-containers",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/azure-health-insights/deploy-portal.md",
10+
"redirect_url": "/previous-versions/azure/azure-health-insights/deploy-portal",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/azure-health-insights/get-started-cli.md",
15+
"redirect_url": "/previous-versions/azure/azure-health-insights/get-started-cli",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "articles/azure-health-insights/get-started-powershell.md",
20+
"redirect_url": "/previous-versions/azure/azure-health-insights/get-started-powershell",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "articles/azure-health-insights/index.yml",
25+
"redirect_url": "/previous-versions/azure/azure-health-insights/index",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "articles/azure-health-insights/overview.md",
30+
"redirect_url": "/previous-versions/azure/azure-health-insights/overview",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "articles/azure-health-insights/reliability-health-insights.md",
35+
"redirect_url": "/previous-versions/azure/azure-health-insights/reliability-health-insights",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "articles/azure-health-insights/use-containers.md",
40+
"redirect_url": "/previous-versions/azure/azure-health-insights/use-containers",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "articles/azure-health-insights/radiology-insights/age-mismatch-inference.md",
45+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/age-mismatch-inference",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "articles/azure-health-insights/radiology-insights/communication-inference.md",
50+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/communication-inference",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "articles/azure-health-insights/radiology-insights/complete-order-discrepancy-inference.md",
55+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/complete-order-discrepancy-inference",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "articles/azure-health-insights/radiology-insights/critical-result-inference.md",
60+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/critical-result-inference",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "articles/azure-health-insights/radiology-insights/faq.md",
65+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/faq",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path": "articles/azure-health-insights/radiology-insights/finding-inference.md",
70+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/finding-inference",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path": "articles/azure-health-insights/radiology-insights/get-started.md",
75+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/get-started",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path": "articles/azure-health-insights/radiology-insights/guidance-inference.md",
80+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/guidance-inference",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path": "articles/azure-health-insights/radiology-insights/index.yml",
85+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/index",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path": "articles/azure-health-insights/radiology-insights/inferences.md",
90+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/inferences",
91+
"redirect_document_id": false
92+
},
93+
{
94+
"source_path": "articles/azure-health-insights/radiology-insights/laterality-mismatch-inference.md",
95+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/laterality-mismatch-inference",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path": "articles/azure-health-insights/radiology-insights/limited-order-discrepancy-inference.md",
100+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/limited-order-discrepancy-inference",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path": "articles/azure-health-insights/radiology-insights/model-configuration.md",
105+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/model-configuration",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path": "articles/azure-health-insights/radiology-insights/overview.md",
110+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/overview",
111+
"redirect_document_id": false
112+
},
113+
{
114+
"source_path": "articles/azure-health-insights/radiology-insights/quality-measure-inference.md",
115+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/quality-measure-inference",
116+
"redirect_document_id": false
117+
},
118+
{
119+
"source_path": "articles/azure-health-insights/radiology-insights/radiology-procedure-inference.md",
120+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/radiology-procedure-inference",
121+
"redirect_document_id": false
122+
},
123+
{
124+
"source_path": "articles/azure-health-insights/radiology-insights/recommendation-inference.md",
125+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/recommendation-inference",
126+
"redirect_document_id": false
127+
},
128+
{
129+
"source_path": "articles/azure-health-insights/radiology-insights/scoring-and-assessment-inference.md",
130+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/scoring-and-assessment-inference",
131+
"redirect_document_id": false
132+
},
133+
{
134+
"source_path": "articles/azure-health-insights/radiology-insights/sex-mismatch-inference.md",
135+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/sex-mismatch-inference",
136+
"redirect_document_id": false
137+
},
138+
{
139+
"source_path": "articles/azure-health-insights/radiology-insights/support-and-help.md",
140+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/support-and-help",
141+
"redirect_document_id": false
142+
},
143+
{
144+
"source_path": "articles/azure-health-insights/radiology-insights/transparency-note.md",
145+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/transparency-note",
146+
"redirect_document_id": false
147+
},
148+
{
149+
"source_path": "articles/azure-health-insights/radiology-insights/tutorial.md",
150+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/tutorial",
151+
"redirect_document_id": false
152+
},
153+
{
154+
"source_path": "articles/azure-health-insights/responsible-ai/data-privacy-security.md",
155+
"redirect_url": "/previous-versions/azure/azure-health-insights/responsible-ai/data-privacy-security",
156+
"redirect_document_id": false
157+
},
158+
{
159+
"source_path": "articles/azure-health-insights/trial-matcher/faq.md",
160+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/faq",
161+
"redirect_document_id": false
162+
},
163+
{
164+
"source_path": "articles/azure-health-insights/trial-matcher/get-started.md",
165+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/get-started",
166+
"redirect_document_id": false
167+
},
168+
{
169+
"source_path": "articles/azure-health-insights/trial-matcher/index.yml",
170+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/index",
171+
"redirect_document_id": false
172+
},
173+
{
174+
"source_path": "articles/azure-health-insights/trial-matcher/inferences.md",
175+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/inferences",
176+
"redirect_document_id": false
177+
},
178+
{
179+
"source_path": "articles/azure-health-insights/trial-matcher/integration-and-responsible-use.md",
180+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/integration-and-responsible-use",
181+
"redirect_document_id": false
182+
},
183+
{
184+
"source_path": "articles/azure-health-insights/trial-matcher/model-configuration.md",
185+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/model-configuration",
186+
"redirect_document_id": false
187+
},
188+
{
189+
"source_path": "articles/azure-health-insights/trial-matcher/overview.md",
190+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/overview",
191+
"redirect_document_id": false
192+
},
193+
{
194+
"source_path": "articles/azure-health-insights/trial-matcher/patient-info.md",
195+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/patient-info",
196+
"redirect_document_id": false
197+
},
198+
{
199+
"source_path": "articles/azure-health-insights/trial-matcher/support-and-help.md",
200+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/support-and-help",
201+
"redirect_document_id": false
202+
},
203+
{
204+
"source_path": "articles/azure-health-insights/trial-matcher/transparency-note.md",
205+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/transparency-note",
206+
"redirect_document_id": false
207+
},
208+
{
209+
"source_path": "articles/azure-health-insights/trial-matcher/trial-matcher-modes.md",
210+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/trial-matcher-modes",
211+
"redirect_document_id": false
212+
},
3213
{
4214
"source_path": "articles/network-watcher/network-watcher-using-open-source-tools.md",
5215
"redirect_url": "/previous-versions/azure/network-watcher/network-watcher-using-open-source-tools",
@@ -6675,6 +6885,11 @@
66756885
"redirect_url": "/azure/reliability/reliability-nat-gateway",
66766886
"redirect_document_id": false
66776887
},
6888+
{
6889+
"source_path": "articles/synapse-analytics/sql/get-started-azure-data-studio.md",
6890+
"redirect_url": "/azure/synapse-analytics/sql/get-started-ssms",
6891+
"redirect_document_id": false
6892+
},
66786893
{
66796894
"source_path": "articles/cyclecloud/how-to/collect-custom-metrics-gpu-infiniband-telegraf.md",
66806895
"redirect_url": "/azure/cyclecloud/how-to/monitor-cyclecloud-cluster-using-prometheus-grafana",

articles/active-directory-b2c/phone-based-mfa.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
title: Securing phone-based MFA in Azure AD B2C
2+
title: Secure phone-based MFA in Azure AD B2C
33
titleSuffix: Azure AD B2C
44
description: Learn tips for securing phone-based multifactor authentication in your Azure AD B2C tenant by using Azure Monitor Log Analytics reports and alerts. Use our workbook to identify fraudulent phone authentications and mitigate fraudulent sign-ups. =
55

66
author: kengaderdus
77
manager: CelesteDG
88
ms.service: azure-active-directory
99
ms.topic: how-to
10-
ms.date: 1/23/2025
10+
ms.date: 02/03/2026
1111
ms.author: kengaderdus
1212
ms.subservice: b2c
1313
ms.custom: sfi-image-nochange
@@ -17,7 +17,7 @@ ms.custom: sfi-image-nochange
1717
#Customer intent: As an Azure AD B2C administrator, I want to monitor phone authentication failures and mitigate fraudulent sign-ups, so that I can protect against malicious use of the telephony service and ensure a secure authentication process.
1818

1919
---
20-
# Securing phone-based multifactor authentication
20+
# Secure phone-based multifactor authentication
2121
[!INCLUDE [active-directory-b2c-end-of-sale-notice-b](../../includes/active-directory-b2c-end-of-sale-notice-b.md)]
2222

2323
With Microsoft Entra multifactor authentication, users can choose to receive an automated voice call at a phone number they register for verification. Malicious users could take advantage of this method by creating multiple accounts and placing phone calls without completing the MFA registration process. These numerous failed sign-ups could exhaust the allowed sign-up attempts, preventing other users from signing up for new accounts in your Azure AD B2C tenant. To help protect against these attacks, you can use Azure Monitor to monitor phone authentication failures and mitigate fraudulent sign-ups.
@@ -144,8 +144,8 @@ To help prevent fraudulent sign-ups, remove any country/region codes that do not
144144
</RelyingParty>
145145
</TrustFrameworkPolicy>
146146
```
147-
> [!IMPORTANT]
148-
>Add the code in step 2 to the _relying party policy_ to enforce country/region code restrictions on the server side. You must not define these elements only in parent policies; put them in the relying party policy.
147+
> [!IMPORTANT]
148+
>Add the code in step 2 to the _relying party policy_ to enforce country/region code restrictions on the server side. You must not define these elements only in parent policies; put them in the relying party policy.
149149

150150
1. In the `BuildingBlocks` section of this policy file, add the following code. Make sure to include only the country/region codes relevant to your organization:
151151

articles/active-directory-b2c/whats-new-docs.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory business-to-customer (B2C)"
33
description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
4-
ms.date: 11/13/2025
4+
ms.date: 02/03/2026
55
ms.service: azure-active-directory
66
ms.subservice: b2c
77
ms.topic: whats-new
@@ -19,6 +19,14 @@ ms.custom: sfi-ropc-nochange
1919

2020
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new and significantly updated docs from the past three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
2121

22+
## January 2026
23+
24+
### Updated articles
25+
26+
- [OAuth 2.0 authorization code flow in Azure Active Directory B2C](authorization-code-flow.md) - Added security guidance on using the `state` parameter
27+
- [Azure Active Directory B2C service limits and restrictions](service-limits.md) - Updated region specific service limits
28+
- [Securing phone-based multifactor authentication](phone-based-mfa.md) - Updated the XML code snippets
29+
2230
## October 2025
2331

2432
### Updated articles
@@ -33,9 +41,3 @@ Welcome to what's new in Azure Active Directory B2C documentation. This article
3341

3442
- [Azure Active Directory B2C service limits and restrictions](service-limits.md) - Added new object limits
3543
- [StringCollection claims transformations](stringcollection-transformations.md) - Updated claim type information
36-
37-
## July 2025
38-
39-
### Updated articles
40-
41-
- [Azure Active Directory B2C service limits and restrictions](service-limits.md) - Added new region limits

0 commit comments

Comments
 (0)