You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/phone-based-mfa.md
+33-9Lines changed: 33 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: kengaderdus
7
7
manager: CelesteDG
8
8
ms.service: azure-active-directory
9
9
ms.topic: how-to
10
-
ms.date: 10/23/2024
10
+
ms.date: 11/05/2025
11
11
ms.author: kengaderdus
12
12
ms.subservice: b2c
13
13
ms.custom: sfi-image-nochange
@@ -93,7 +93,7 @@ Take the following actions to help mitigate fraudulent sign-ups.
93
93
-[Configure a Conditional Access policy](conditional-access-user-flow.md) to block sign-ins based on location (applies to sign-in flows only, not sign-up flows).
94
94
- To prevent automated attacks on your consumer-facing apps, [enable CAPTCHA](add-captcha.md). Azure AD B2C’s CAPTCHA supports both audio and visual CAPTCHA challenges, and applies to both sign-up and sign-in flows for your local accounts.
95
95
96
-
- Remove country codes that aren't relevant to your organization from the drop-down menu where the user verifies their phone number (this change will apply to future sign-ups):
96
+
- Remove country/region codes that aren't relevant to your organization from the drop-down menu where the user verifies their phone number (this change will apply to future sign-ups):
97
97
98
98
1. Sign in to the [Azure portal](https://portal.azure.com) as the [External ID User Flow Administrator](/entra/identity/role-based-access-control/permissions-reference#external-id-user-flow-administrator) of your Azure AD B2C tenant.
99
99
1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Azure AD B2C tenant from the **Directories + subscriptions** menu.
@@ -104,9 +104,9 @@ Take the following actions to help mitigate fraudulent sign-ups.
104
104
105
105
1. Open the JSON file that was downloaded in the previous step. In the file, search for `DEFAULT`, and replace the line with `"Value": "{\"DEFAULT\":\"Country/Region\",\"US\":\"United States\"}"`. Be sure to set `Overrides` to `true`.
106
106
107
-
To implement SMS blocking effectively, make sure the Overrides setting is enabled (set to true) only for your organization’s primary or default language. Do not enable Overrides for any secondary or non-primary languages, as this can cause unexpected SMS blocking. Since the countryList in the JSON file acts as an allow list, be sure to include all countries that should be permitted to send SMS in this list for the primary language configuration when Overrides is true.
107
+
To implement SMS blocking effectively, make sure the Overrides setting is enabled (set to true) only for your organization’s primary or default language. Do not enable Overrides for any secondary or non-primary languages, as this can cause unexpected SMS blocking. Since the countryList in the JSON file acts as an allow list, be sure to include all countries/regions that should be permitted to send SMS in this list for the primary language configuration when Overrides is true.
108
108
> [!NOTE]
109
-
> You can customize the list of allowed country codes in the `countryList` element (see the [Phone factor authentication page example](localization-string-ids.md#phone-factor-authentication-page-example)).
109
+
> You can customize the list of allowed country/region codes in the `countryList` element (see the [Phone factor authentication page example](localization-string-ids.md#phone-factor-authentication-page-example)).
110
110
111
111
1. Save the JSON file. In the language details panel, under **Upload new overrides**, select the modified JSON file to upload it.
112
112
1. Close the panel and select **Run user flow**. For this example, confirm that **United States** is the only country code available in the dropdown:
@@ -115,11 +115,32 @@ Take the following actions to help mitigate fraudulent sign-ups.
115
115
116
116
## Mitigate fraudulent sign-ups for custom policy
117
117
118
-
To help prevent fraudulent sign-ups, remove any country codes that do not apply to your organization by following these steps:
118
+
To help prevent fraudulent sign-ups, remove any country/region codes that do not apply to your organization by following these steps:
119
119
120
-
1. Locate the policy file that defines the `RelyingParty`. For example, in the [Starter Pack](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack), this is usually the SignUpOrSignin.xml file.
120
+
1. Locate the policy file that defines the `RelyingParty`. For example, in the [Starter Pack](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack), this is usually the SignUpOrSignin.xml file. See the following snippet.
121
121
122
-
1. In the `BuildingBlocks` section of this policy file, add the following code. Make sure to include only the country codes relevant to your organization:
<!-- Add the XML code outlined in Step 2 if this section. -->
135
+
</BuildingBlocks>
136
+
137
+
<RelyingParty>
138
+
...
139
+
</RelyingParty>
140
+
</TrustFrameworkPolicy>
141
+
```
142
+
143
+
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:
123
144
124
145
```xml
125
146
<BuildingBlocks>
@@ -155,10 +176,13 @@ To help prevent fraudulent sign-ups, remove any country codes that do not apply
155
176
</BuildingBlocks>
156
177
```
157
178
158
-
The countryList acts as an allow list. Only the countries you specify in this list (for example, Japan, Bulgaria, and the United States) are permitted to use MFA. All other countries are blocked.
179
+
The countryList acts as an allow list. Only the countries/regions you specify in this list (for example, Japan, Bulgaria, and the United States) are permitted to use MFA. All other countries/regions are blocked.
180
+
181
+
> [!IMPORTANT]
182
+
> This code must be added to the relying party policy to ensure the country/region code restrictions are properly enforced on the server side.
159
183
160
184
## Related content
161
185
162
186
- Learn about [Identity Protection and Conditional Access for Azure AD B2C](conditional-access-identity-protection-overview.md)
163
187
164
-
- Apply [Conditional Access to user flows in Azure Active Directory B2C](conditional-access-user-flow.md)
188
+
- Apply [Conditional Access to user flows in Azure Active Directory B2C](conditional-access-user-flow.md)
Copy file name to clipboardExpand all lines: articles/application-gateway/private-link-configure.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: application-gateway
6
6
author: mbender-ms
7
7
ms.service: azure-application-gateway
8
8
ms.topic: how-to
9
-
ms.date: 07/09/2025
9
+
ms.date: 11/5/2025
10
10
ms.author: mbender
11
11
ms.custom:
12
12
- devx-track-azurecli, devx-track-azurepowershell
@@ -72,6 +72,9 @@ Follow these steps to create the Private Link configuration:
72
72
6. Select **Add** to create the configuration.
73
73
7. From your Application Gateway settings, copy and save the **Resource ID**. This identifier is required when setting up Private Endpoints from different Microsoft Entra tenants.
74
74
75
+
>[!CAUTION]
76
+
>Private link configuration will momentarily cause traffic disruption (less than 1 minute) while the change is applied. Changes are recommended to be conducted during a maintenance window or period of low-traffic. During this time, you may see connection timeouts or 4XX http status codes returned on request. Add/Remove/Approval/Rejection of private endpoints will not cause traffic disruption.
77
+
75
78
## Configure Private Endpoint
76
79
77
80
A Private Endpoint is a network interface that uses a private IP address from your virtual network to connect securely to Azure Application Gateway. Clients use the Private Endpoint's private IP address to establish connections to the Application Gateway through a secure tunnel.
Copy file name to clipboardExpand all lines: articles/cost-management-billing/understand/mca-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Roles on the billing profiles have permissions to view and manage invoices and p
39
39
40
40
### Each billing profile gets a monthly invoice
41
41
42
-
A monthly invoice is generated at the beginning of the month for each billing profile. The invoice contains all charges from the previous month.
42
+
A monthly invoice is generated at the beginning of the month for each billing profile. The invoice contains all usage charges from the previous month. Seat-based subscriptions will be billed separately.
43
43
44
44
You can view the invoice, download documents, and the change setting to get future invoices by email, in the Azure portal. For more information, see [download invoices for a Microsoft Customer Agreement](../manage/download-azure-invoice-daily-usage-date.md#download-invoices-for-a-microsoft-customer-agreement).
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/billing.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,19 +2,25 @@
2
2
title: Microsoft Defender for IoT billing
3
3
description: Learn how you're billed for the Microsoft Defender for IoT service.
4
4
ms.topic: concept-article
5
-
ms.date: 03/25/2024
5
+
ms.date: 11/05/2025
6
6
ms.custom: enterprise-iot
7
7
#CustomerIntent: As a Defender for IoT customer, I want to understand how I'm billed for Defender for IoT services so that I can best plan my deployment.
8
8
---
9
9
10
10
# Defender for IoT billing
11
11
12
+
> [!NOTE]
13
+
> This article is relevant for commercial Defender for IoT customers.
14
+
> If you're a government customer, see [government customers trial license](getting-started.md#government-customers-trial-license) or contact your Microsoft sales representative for more information.
15
+
16
+
12
17
As you plan your Microsoft Defender for IoT deployment, you typically want to understand the Defender for IoT pricing plans and billing models so you can optimize your costs.
13
18
14
19
**OT monitoring** is billed using site-based licenses, where each license applies to an individual site, based on the site size. A site is a physical location, such as a facility, campus, office building, hospital, rig, and so on. Each site can contain any number of network sensors, all of which monitor devices detected in connected networks.
15
20
16
21
**Enterprise IoT monitoring** supports 5 devices per Microsoft 365 E5 (ME5) or E5 Security license, or is available as standalone, per-device licenses for Microsoft Defender for Endpoint P2 customers.
17
22
23
+
18
24
## Free trial
19
25
20
26
To evaluate Defender for IoT, start a free trial as follows:
0 commit comments