Microsoft Azure News
Generally Available: Storage account default egress limit increase to 200 Gbps
The default maximum egress for general-purpose v2 and Blob storage accounts has been increased from 120 Gbps to 200 Gbps in the following regions:
- East Asia
- Southeast Asia
- Australia East
- Brazil South
- Canada Central
- China East 2
- China North 3
- North Europe
- West Europe
- France Central
- Germany West Central
- Central India
- Japan East
- Jio India West
- Korea Central
- Norway East
- South Africa North
- Sweden Central
- UAE North
- UK South
- Central US
- East US
- East US 2
- USGov Virginia
- USGov Arizona
- North Central US
- South Central US
- West US
- West US 2
- West US 3
This applies to all existing and new storage accounts.
Generally Available: Several performance management server parameters now modifiable on Azure Database for PostgreSQL
Published date: Oct 10, 2024
Related Products
We’re thrilled to announce that you can now modify a number of performance management server parameters in Azure Database for PostgreSQL – Flexible Server.
You now have the ability to specify the maximum number of parallel apply workers per subscription, and modify temp_file_limit, logical_decoding_work_mem, idle_session_timeout, enable_incremental_sort, and log_hostname in Azure Database for PostgreSQL.
Public Preview: vCore-based Azure Cosmos DB for MongoDB multishard, cross-region replication
Published date: Oct 10, 2024
With cross-region replication extended to multishard configurations of vCore-based Azure Cosmos DB for MongoDB clusters, you can create a replica cluster in another region for disaster recovery and for improved read scalability.
Once created, a cluster replica is continuously updated with the data written to the primary region. In the rare case of an outage in the primary region, you can promote the cluster replica, making it the new read-write cluster.
When you promote the cluster replica in region B and make it the new read-write cluster, it swaps roles with the cluster in region A. Connection strings for the cluster in region A and the cluster in region B are preserved after replica promotion.
You can use the cluster replica in another region to offload read operations from the primary cluster. The read replica in the other region also delivers reads with lower latency to applications that are hosted in or closer to that region.
Public Preview: vCore-based Azure Cosmos DB for MongoDB multishard clusters
Published date: Oct 10, 2024
You can now use up to five physical shards on your vCore-based Azure Cosmos DB for MongoDB clusters. An increased number of shards in a cluster enables you to host larger workloads.
When you create a vCore-based Azure Cosmos DB for MongoDB cluster, you can select from one to five shards. As before, each physical shard gets the same compute (vCore count and amount of RAM) and storage (GiB and IOPS) configuration.
Using a greater number of physical shards can also help increase cluster performance for larger workloads that require multishard clusters because of better parallelisation.
Generally Available: Dedicated gateway RBAC support and a new request option
Published date: Oct 10, 2024
Get more flexibility in how you authenticate to the dedicated gateway as well as which dedicated gateway requests use the integrated cache. Support for RBAC authentication using Microsoft Entra ID allows you to connect to the dedicated gateway without relying on the primary key to your Azure Cosmos DB account. Additionally, the request option to bypass the integrated cache gives you fine-grained control over which dedicated gateway requests are sent straight to the database. Allowing some requests to bypass the cache means you can optimise your cache space with the items and queries that are most likely to be repeated and lower the risk of frequently read data being evicted.
Important notice: Your customer has unused Azure subscription(s) that will soon be blocked
In November 2024, Microsoft will begin blocking and eventually terminate Azure subscriptions that have not been used for more than 12 months. Account owner and service admins of the subscription will be notified 30 days before the block is applied. If no action is taken, the subscriptions will be terminated 90 days after the block.