This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 23%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERV%3C/text%3E%3C/svg%3E)
Why is the learn documentation "Repository Not Currently Accepting Public Contributions". I have found mistakes but cannot request a change.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 2%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
Hi obert Virnau,
Thank you for reaching out to us on Microsoft Q&A forum. Can you please specify the exact Learn Path/Module name/Exercise link where you are encountering this error along with the screenshots for reference.
Hi obert Virnau,
Can you please specify the exact Learn Path/Module name/Exercise link where you are encountering this error along with the screenshots for reference.
I think this is incorrect in the documentation "You can also deploy Azure SQL Database into Availability Zones."
I think the documentation should say something like "You can also deploy VMs running SQL Database into Availability Zones to provide zone redundancy.", particularly because this section is about VMs. If the goal is to teach that Azure Database can use availability zones maybe it should say "You can also deploy Azure SQL Database into availability zones by setting up Azure SQL Database to use zone redundancy". And maybe provide a link to how to do it (like https://techcommunity.microsoft.com/blog/azuresqlblog/zone-redundancy-for-azure-sql-database-general-purpose-tier/3280376)
Located in Unit 4 of "Describe high availability and disaster recovery strategies" https://learn.microsoft.com/en-us/training/modules/describe-high-availability-disaster-recovery-strategies/4-describe-azure-high-availability-disaster-recovery-features, Unit 4 covers "Describe Azure high availability and disaster recovery features for Azure Virtual Machines".
A bit more detail about this...
I think it is one of those situations where the terminology is so similar it gets confusing.
Availability Zones are physically separate locations within an Azure region, each with its own power, cooling, and networking. They provide high availability and resilience by distributing resources across multiple zones to protect against datacenter-level failures.
Zone Redundancy is a feature that replicates data or resources across multiple availability zones within a region. This ensures that data or services remain available even if one zone experiences a failure.
Soo,
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
Azure SQL Database can be deployed into Availability Zones.
High availability through zone-redundancy
Zone-redundant availability ensures your data is spread across three Azure availability zones in the primary region. Each availability zone is a separate physical location with independent power, cooling, and networking.
Zone-redundant availability is available to databases in the Business Critical, General Purpose and Hyperscale service tiers of the vCore-based purchasing model, and only the Premium service tier of the DTU-based purchasing model - the Basic and Standard service tiers don't support zone redundancy.
While each service tier implements zone-redundancy differently, All implementations ensure a Recovery Point Objective (RPO) with zero loss of committed data upon failover.
General Purpose service tier
Zone-redundant configuration for the General Purpose service tier is offered for both serverless and provisioned compute for databases in vCore purchasing model. This configuration utilizes Azure Availability Zones to replicate databases across multiple physical locations within an Azure region. By selecting zone-redundancy, you can make your new and existing serverless and provisioned general purpose single databases and elastic pools resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes of the application logic.
Zone-redundant configuration for the General Purpose tier has two layers:
tempdb and model databases on the attached SSD, and plan cache, buffer pool, and columnstore pool in memory. This stateless node is operated by Azure Service Fabric that initializes sqlservr.exe, controls health of the node, and performs failover to another node if necessary. For zone-redundant serverless and provisioned General Purpose databases, nodes with spare capacity are readily available in other Availability Zones for failover.If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin
Follow https://learn.microsoft.com/en-us/contribute/
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin
Thank you, however the documentation says it is not open for contributions, and the "report an issue: link is no longer at the bottom of the learning unit (as it once was).
Azure SQL Database can be deployed into Availability Zones.
High availability through zone-redundancy
Zone-redundant availability ensures your data is spread across three Azure availability zones in the primary region. Each availability zone is a separate physical location with independent power, cooling, and networking.
Zone-redundant availability is available to databases in the Business Critical, General Purpose and Hyperscale service tiers of the vCore-based purchasing model, and only the Premium service tier of the DTU-based purchasing model - the Basic and Standard service tiers don't support zone redundancy.
While each service tier implements zone-redundancy differently, All implementations ensure a Recovery Point Objective (RPO) with zero loss of committed data upon failover.
General Purpose service tier
Zone-redundant configuration for the General Purpose service tier is offered for both serverless and provisioned compute for databases in vCore purchasing model. This configuration utilizes Azure Availability Zones to replicate databases across multiple physical locations within an Azure region. By selecting zone-redundancy, you can make your new and existing serverless and provisioned general purpose single databases and elastic pools resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes of the application logic.
Zone-redundant configuration for the General Purpose tier has two layers:
tempdb and model databases on the attached SSD, and plan cache, buffer pool, and columnstore pool in memory. This stateless node is operated by Azure Service Fabric that initializes sqlservr.exe, controls health of the node, and performs failover to another node if necessary. For zone-redundant serverless and provisioned General Purpose databases, nodes with spare capacity are readily available in other Availability Zones for failover.If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin
My apologies for the "redundancy" :)
Just to make it a bit clearer, the part of the document I mention is for unit 4 of "Describe high availability and disaster recovery strategies". Unit 4 covers "Describe Azure high availability and disaster recovery features for Azure Virtual Machines". I think it is one of those situations where the terminology is so similar it gets confusing.
Availability Zones are physically separate locations within an Azure region, each with its own power, cooling, and networking. They provide high availability and resilience by distributing resources across multiple zones to protect against datacenter-level failures.
Zone Redundancy is a feature that replicates data or resources across multiple availability zones within a region. This ensures that data or services remain available even if one zone experiences a failure.
Soo,
Agreed - appreciate the explanation. I think these nuances are properly captured in the Microsoft Learn content (not training). The latter does leave room for improvement.
Unfortunately, as you pointed out, it appears that updates to that specific content are simply no longer accepted...
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin
Hi Robert Virnau,
I wanted to check if you had the chance to review the information that was provided by Marcin Policht. Please feel free to contact us if you have any more queries. If you feel that the provided response is helpful, provide your accepted answer by clicking Accept the answer. So that other community members can benefit from the information.
Hi Robert Virnau,
I wanted to check if you had the chance to review the information that was provided by Marcin Policht. If you feel that the provided response is helpful, provide your accepted answer by clicking Accept the answer. So that other community members can benefit from the information.