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
<!-- Add this BuildingBlocks section to the relying party policy. -->
133
138
<BuildingBlocks>
134
-
<!-- Add the XML code outlined in Step 2 if this section. -->
139
+
<!-- Add the XML code outlined in Step 2 in this section. -->
135
140
</BuildingBlocks>
136
141
137
142
<RelyingParty>
138
143
...
139
144
</RelyingParty>
140
145
</TrustFrameworkPolicy>
141
146
```
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.
142
149
143
150
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:
144
151
@@ -178,11 +185,8 @@ To help prevent fraudulent sign-ups, remove any country/region codes that do not
178
185
179
186
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
187
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.
188
+
183
189
184
190
## Related content
185
191
186
192
- Learn about [Identity Protection and Conditional Access for Azure AD B2C](conditional-access-identity-protection-overview.md)
187
-
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/active-directory-b2c/service-limits.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: CelesteDG
8
8
ms.service: azure-active-directory
9
9
10
10
ms.topic: reference
11
-
ms.date: 01/08/2026
11
+
ms.date: 01/22/2026
12
12
ms.subservice: b2c
13
13
zone_pivot_groups: b2c-policy-type
14
14
@@ -186,7 +186,7 @@ The following table lists the administrative configuration limits in the Azure A
186
186
187
187
## Region specific service limits
188
188
189
-
As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits. These limits apply to both SMS and Voice verification.
189
+
As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits. Only SMS verification is subject to these limits.
190
190
191
191
| Region Code | Region Name | Limit per tenant per 60 minutes | Limit per tenant per 24 hours |
Copy file name to clipboardExpand all lines: articles/app-service/includes/configure-azure-storage/azure-storage-linux-container-pivot.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
author: msangapu-msft
3
3
ms.service: azure-app-service
4
4
ms.topic: include
5
-
ms.date: 03/04/2025
5
+
ms.date: 01/23/2026
6
6
ms.author: msangapu
7
7
ms.custom:
8
8
- linux-related-content
@@ -238,6 +238,7 @@ You can customize health‑check behavior using the following app settings.
238
238
| Azure Blob |`WEBSITE_BYOS_BLOB_HEALTH_CHECK_FREQUENCY`|`5`| Interval in seconds between health checks. |
239
239
| Azure Blob |`WEBSITE_BYOS_BLOB_MAX_FAILED_PINGS`|`15`| Number of consecutive failures before marking the volume as faulted. |
240
240
| Azure Blob |`WEBSITE_BYOS_BLOB_AUTO_RECOVERY_ENABLED`|`true`| Set to `false` to disable auto‑recovery logic. |
241
+
| Azure Blob |`WEBSITE_BYOS_BLOB_DIRECT_IO`|`false`| If enabled, all transactions will query the remote storage directly and caching will be bypassed. This setting is applied at the application level and therefore affects all blob shares mounted by the application. |
|`WEBSITE_CONTENTAZUREFILECONNECTIONSTRING`| By default, App Service creates a shared storage for you at app creation. To use a custom storage account instead, set to the connection string of your storage account. For functions, see [App settings reference for Azure Functions](../azure-functions/functions-app-settings.md#website_contentazurefileconnectionstring).<br/><br/>Example: `DefaultEndpointsProtocol=https;AccountName=<name>;AccountKey=<key>`|
50
50
|`WEBSITE_CONTENTSHARE`| When you use specify a custom storage account with `WEBSITE_CONTENTAZUREFILECONNECTIONSTRING`, App Service creates a file share in that storage account for your app. To use a custom name, set this variable to the name that you want. If a file share with the specified name doesn't exist, App Service creates it for you.<br/><br/>Example: `myapp123`|
51
+
|`WEBSITE_BYOS_BLOB_DIRECT_IO`| Set to `false` by default. If enabled, all transactions will query the remote storage directly and caching will be bypassed. This setting is applied at the application level and therefore affects all blob shares mounted by the application.<br/><br/> Only relevant when using custom-mounted Azure Blob Storage. Applicable to Linux containers only (not applicable to Windows). |
51
52
|`WEBSITE_SCM_ALWAYS_ON_ENABLED`| Read-only. Shows whether Always On is enabled (`1`) or not (`0`). |
52
53
|`WEBSITE_SCM_SEPARATE_STATUS`| Read-only. Shows whether the Kudu app is running in a separate process (`1`) or not (`0`). |
53
54
|`WEBSITE_DNS_ATTEMPTS`| Number of times to try name resolution. |
0 commit comments