Skip to content

Commit 00e5abe

Browse files
authored
Merge pull request #293320 from MicrosoftDocs/main
1/21/2025 AM Publish
2 parents c84ddaf + 07b6273 commit 00e5abe

13 files changed

+98
-45
lines changed

articles/active-directory-b2c/service-limits.md

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -177,6 +177,51 @@ The following table lists the administrative configuration limits in the Azure A
177177

178178
<sup>1</sup> See also [Microsoft Entra service limits and restrictions](../active-directory/enterprise-users/directory-service-limits-restrictions.md).
179179

180+
## Region specific service limits
181+
182+
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.
183+
184+
| Region Code | Region Name | Limit per tenant per 60 minutes | Limit per tenant per 24 hours |
185+
|:----------- |:---------------------------------------------- |:------------------------------- | :----------------------------------------|
186+
| 228 | Togo | 10 | 30 |
187+
| 257 | Uzbek | 10 | 30 |
188+
| 970 | State of Plaestine | 10 | 30 |
189+
| 249 | Sudan | 10 | 30 |
190+
| 226 | Burina Faso | 10 | 30 |
191+
| 252 | Somalia | 10 | 30 |
192+
| 501 | Belize | 10 | 30 |
193+
| 855 | Cambodia | 50 | 200 |
194+
| 84 | Vietnam | 150 | 500 |
195+
| 94 | Sri Lanka | 100 | 500 |
196+
| 63 | Philippines | 50 | 200 |
197+
| 62 | Indonesia | 50 | 200 |
198+
| 7 | Russia | 100 | 1000 |
199+
| 258 | Mozambique | 50 | 200 |
200+
| 92 | Pakistan | 100 | 1000 |
201+
| 994 | Azerbaijan | 50 | 200 |
202+
| 880 | Bangladesh | 50 | 200 |
203+
| 20 | Egypt | 50 | 200 |
204+
| 260 | Zambia | 50 | 200 |
205+
| 502 | Guatemala | 10 | 50
206+
| 255 | Tanzania | 10 | 50
207+
| 261 | Madagascar | 10 | 30
208+
| 998 | Uzbekistan | 10 | 30
209+
| 223 | Mali | 20 | 100
210+
| 52 | Mexico | 100 | 500
211+
| 60 | Malaysia | 50 | 200 |
212+
| 221 | Senegal | 10 | 30 |
213+
| 216 | Tunisia | 20 | 100 |
214+
| 503 | El Salvador | 10 | 30 |
215+
| 234 | Nigeria | 20 | 100 |
216+
| 386 | Slovenia | 10 | 50 |
217+
| 591 | Bolivia | 10 | 30 |
218+
| 263 | Zimbabwe | 10 | 30 |
219+
| 261 | Madagascar | 10 | 30 |
220+
| 995 | Georgia | 10 | 30 |
221+
| 993 | Turkmenistan | 10 | 30 |
222+
| 256 | Uganda | 20 | 100 |
223+
| 212 | Moroccoa | 20 | 100 |
224+
180225
## Next steps
181226

182227
- Learn about [Microsoft Graph's throttling guidance](/graph/throttling)

articles/bastion/session-recording.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to configure and record Bastion sessions.
55
author: cherylmc
66
ms.service: azure-bastion
77
ms.topic: how-to
8-
ms.date: 06/21/2024
8+
ms.date: 01/21/2025
99
ms.author: cherylmc
1010

1111
---
@@ -57,7 +57,7 @@ If you've already deployed Bastion, use the following steps to enable session re
5757
1. In the Azure portal, go to your Bastion resource.
5858
1. On your Bastion page, in the left pane, select **Configuration**.
5959
1. On the Configuration page, for Tier, select **Premium** if it isn't already selected. This feature requires the Premium SKU.
60-
1. Select **Session Recording (Preview)** from the listed features.
60+
1. Select **Session Recording** from the listed features.
6161
1. Select **Apply**. Bastion immediately begins updating the settings for your bastion host. Updates take about 10 minutes.
6262

6363
## Configure storage account container

articles/communications-gateway/interoperability-operator-connect.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Your core mobile network must supply this information to Azure Communications Ga
4444
Your core mobile network must also be able to anchor and divert calls into the Microsoft Phone System. You can choose from the following options.
4545

4646
- Using Mobile Control Point (MCP) in Azure Communications Gateway. MCP is an IMS Application Server that queries the Teams Phone Mobile Consultation API to determine whether the call involves a Teams Phone Mobile Subscriber. MCP then adds X-MS-FMC headers and updates the signaling to divert the call into the Microsoft Phone System through Azure Communications Gateway. For more information, see [Mobile Control Point in Azure Communications Gateway for Teams Phone Mobile](mobile-control-point.md).
47-
- Deploying an on-premises version of Mobile Control Point (MCP) from Metaswitch. For more information, see the [Metaswitch description of Mobile Control Point](https://www.metaswitch.com/products/mobile-control-point). This version of MCP isn't included in Azure Communications Gateway.
47+
- Deploying an on-premises version of Mobile Control Point (MCP) from Metaswitch. For more information, see the [Metaswitch description of Mobile Control Point](https://info.metaswitch.com/hubfs/pdfs/MobileControlPoint_How%20it%20Works.pdf). This version of MCP isn't included in Azure Communications Gateway.
4848
- Using other routing capabilities in your core network to detect Teams Phone Mobile subscribers and route INVITEs to or from these subscribers into the Microsoft Phone System through Azure Communications Gateway.
4949

5050
> [!IMPORTANT]

articles/firewall/firewall-faq.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,9 @@ sections:
156156
- The firewall's region [supports availability zones](../reliability/availability-zones-region-support.md).
157157
- All attached public IP addresses are deployed with availability zones. In the properties page of each public IP address, ensure the **availability zones** field exists and is configured with the same zones you configured for the firewall.
158158
159-
Reconfiguring availability zones can only be done when you restart the firewall. After you allocate the firewall, and right before starting the firewall with `Set-AzFirewall`, use the following Azure PowerShell to modify the firewall's **Zones** property:
159+
Reconfiguring availability zones can only be done when you restart the firewall. First you need to deallocate the firewall (by using '$azfw.Deallocate()'), then change the zone configuration and then allocate the firewall (by using '$azfw.Allocate()').
160+
161+
After you allocate the firewall, and right before starting the firewall with `Set-AzFirewall`, use the following Azure PowerShell to modify the firewall's **Zones** property:
160162
161163
```azurepowershell
162164
$azfw = Get-AzFirewall -Name "FW Name" -ResourceGroupName "RG Name"

articles/firewall/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 02/26/2024
1313

1414
# What is Azure Firewall?
1515

16-
Azure Firewall is a cloud-native and intelligent network firewall security service that provides the best of breed threat protection for your cloud workloads running in Azure. It's a fully stateful firewall as a service with built-in high availability and unrestricted cloud scalability. It provides both east-west and north-south traffic inspection. To learn what's east-west and north-south traffic, see [East-west and north-south traffic](/azure/architecture/framework/security/design-network-flow#east-west-and-north-south-traffic).
16+
Azure Firewall is a cloud-native and intelligent network firewall security service that provides the best of breed threat protection for your cloud workloads running in Azure. It's a fully stateful firewall as a service with built-in high availability and unrestricted cloud scalability. It provides both east-west and north-south traffic inspection. To learn what's east-west and north-south traffic, see [East-west and north-south traffic](/azure/well-architected/security/networking#scope-of-influence).
1717

1818
Azure Firewall is offered in three SKUs: Standard, Premium, and Basic.
1919

articles/iot-edge/support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ The systems listed in the following table are considered compatible with Azure I
106106

107107
| Operating System | AMD64 | ARM32v7 | ARM64 | End of OS provider standard support |
108108
| ---------------- | ----- | ------- | ----- | -------------- |
109-
| [CentOS-7](https://docs.centos.org/en-US/docs/) | ![CentOS + AMD64](./media/support/green-check.png) | ![CentOS + ARM32v7](./media/support/green-check.png) | ![CentOS + ARM64](./media/support/green-check.png) | [June 2024](https://www.redhat.com/en/topics/linux/centos-linux-eol). For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life). |
109+
| [CentOS-7](https://docs.centos.org/) | ![CentOS + AMD64](./media/support/green-check.png) | ![CentOS + ARM32v7](./media/support/green-check.png) | ![CentOS + ARM64](./media/support/green-check.png) | [June 2024](https://www.redhat.com/en/topics/linux/centos-linux-eol). For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life). |
110110
| [Debian 10 <sup>1</sup>](https://www.debian.org/releases/buster/) | ![Debian 10 + AMD64](./media/support/green-check.png) | ![Debian 10 + ARM32v7](./media/support/green-check.png) | ![Debian 10 + ARM64](./media/support/green-check.png) | [June 2024](https://wiki.debian.org/LTS) |
111111
| [Debian 11](https://www.debian.org/releases/bullseye/) | ![Debian 11 + AMD64](./media/support/green-check.png) | | ![Debian 11 + ARM64](./media/support/green-check.png) | [June 2026](https://wiki.debian.org/LTS) |
112112
| [Mentor Embedded Linux Flex OS](https://www.mentor.com/embedded-software/linux/mel-flex-os/) | ![Mentor Embedded Linux Flex OS + AMD64](./media/support/green-check.png) | ![Mentor Embedded Linux Flex OS + ARM32v7](./media/support/green-check.png) | ![Mentor Embedded Linux Flex OS + ARM64](./media/support/green-check.png) | |

articles/iot/iot-overview-device-development.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: iot
66
author: dominicbetts
77
ms.author: dobett
88
ms.topic: overview
9-
ms.date: 02/28/2024
9+
ms.date: 01/20/2025
1010
ms.custom: template-overview
1111
# Customer intent: As a solution builder or asset/device developer I want a high-level overview of the issues around asset and device development so that I can easily find relevant content.
1212
---

articles/reliability/concept-shared-responsibility.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The shared responsibility model for resiliency is composed of three levels:
2828

2929
Microsoft is solely responsible for core platform reliability. Microsoft is also responsible for providing resilience-enhancing capabilities that you can use. You're responsible for selecting and using the appropriate components.
3030

31-
Whether you choose SaaS, PaaS, or IaaS service categories determines what kind of decisions you make. For example, if you use an SaaS service, you typically don't need to opt into using availability zones. If you use PaaS services for your data tier, you might have automated capabilities for backup available to you. If you use IaaS services, you typically need to plan and implement many resiliency capabilities yourself.
31+
Whether you choose SaaS, PaaS, or IaaS service categories determines what kind of decisions you make. For example, if you use a SaaS service, you typically don't need to opt into using availability zones. If you use PaaS services for your data tier, you might have automated capabilities for backup available to you. If you use IaaS services, you typically need to plan and implement many resiliency capabilities yourself.
3232

3333
> [!NOTE]
3434
> Service categories (SaaS, PaaS, and IaaS) are useful as a broad grouping of services, but it's important to understand your responsibilities for each individual service you use.

articles/reliability/regions-paired.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ The table below lists Azure region pairs:
5555
| **France** | France Central | France South\* |
5656
| **Germany** | Germany West Central | Germany North\* |
5757
| **India** | Central India | South India |
58-
| |Central India | West India |
58+
| |South India | Central India |
5959
| | West India | South India |
6060
| **Japan** | Japan East | Japan West |
6161
| **Korea** | Korea Central | Korea South\* |

0 commit comments

Comments
 (0)