From 57cc69e905eb49d1557798620da37546b975b166 Mon Sep 17 00:00:00 2001 From: Nick Gagliardi Date: Wed, 25 Feb 2026 13:59:57 -0500 Subject: [PATCH 1/2] docs: update private cloud region documentation --- .../private-cloud-on-aws.mdx | 65 ++++-- .../private-cloud-on-azure.mdx | 70 ++++-- .../private-cloud-region-support.mdx | 216 ++++++++++++++++++ 3 files changed, 315 insertions(+), 36 deletions(-) create mode 100644 main/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support.mdx diff --git a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws.mdx b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws.mdx index 0c00d75dfe..47e9e36899 100644 --- a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws.mdx +++ b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws.mdx @@ -116,28 +116,59 @@ Guaranteed requests per second (RPS) and SLA do not apply to non-production envi ### Data Center Locations -Private Cloud on AWS is fully deployable in the following regions: +Auth0 Private Cloud on AWS is available in multiple regions worldwide. All regions listed below have been validated for production deployment and meet Auth0's high availability and performance standards. -* Australia +#### Production-Ready Regions + +The following AWS regions are **fully validated and production-ready** for immediate deployment: + +* Australia (Sydney) * Bahrain -* Brazil -* Canada -* France -* Germany +* Brazil (São Paulo) +* Canada (Central) +* France (Paris) +* Germany (Frankfurt) * Hong Kong -* India -* Indonesia -* Ireland -* Italy -* Japan -* Mexico +* India (Mumbai, Hyderabad) +* Ireland (Dublin) +* Italy (Milan) +* Japan (Tokyo) +* Mexico (Central) * Singapore -* South Africa -* South Korea -* Sweden +* South Korea (Seoul) +* Sweden (Stockholm) * United Arab Emirates (UAE) -* United Kingdom -* USA +* United Kingdom (London) +* USA (Multiple regions) + + + All production-ready regions have undergone rigorous validation including: + - Multi-availability zone deployment verification + - High availability (GeoHA) pairing validation + - Performance and capacity testing + - Security and compliance review + + +#### Additional Regions Available Upon Request + +Auth0 can validate and deploy Private Cloud in additional AWS regions to meet your data residency requirements. Region validation ensures production-grade reliability and performance before deployment. + +**Validation process:** +- **Timeline:** Typically 1-4 weeks depending on region complexity +- **Scope:** Multi-AZ deployment, capacity verification, GeoHA pairing (if applicable) +- **Requirements:** Active Private Cloud contract or purchase order + +To request validation for a specific AWS region: +1. Contact your Auth0 Account Executive or Technical Account Manager +2. Provide your preferred region(s) and timeline requirements +3. Auth0 will assess feasibility and provide a validation timeline +4. Deployment proceeds after successful validation + + + **Planning Ahead:** Request region validation during your sales cycle to ensure your preferred region is ready for deployment at contract start. Last-minute requests may delay your implementation timeline. + + +For detailed information about the region validation process, see [Private Cloud Region Support](/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support). ### Bursty Traffic diff --git a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure.mdx b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure.mdx index 9329835dc4..87582957aa 100644 --- a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure.mdx +++ b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure.mdx @@ -100,25 +100,57 @@ Guaranteed requests per second (RPS) and SLA do not apply to non-production envi ### Data Center Locations -Private Cloud on Azure is fully deployable in the following regions: - -* Australia -* Brazil -* Canada -* France -* Germany -* India -* Ireland -* Japan -* Netherlands -* Norway -* South Africa -* South Korea -* Sweden -* Switzerland -* United Arab Emirates -* United Kingdom -* USA +Auth0 Private Cloud on Azure is available in multiple regions worldwide. All regions listed below have been validated for production deployment and meet Auth0's high availability and performance standards. + +#### Production-Ready Regions + +The following Azure regions are **fully validated and production-ready** for immediate deployment: + +* Australia (East) +* Brazil (South) +* Canada (Central) +* France (Central) +* Germany (West Central) +* Ireland (West Europe) +* Japan (East) +* South Korea (Central) +* Sweden (Central) +* United Kingdom (South) +* USA (Multiple regions) + + + All production-ready regions have undergone rigorous validation including: + - Three availability zone deployment verification + - High availability (GeoHA) pairing validation (if applicable) + - Azure capacity and quota verification + - Performance and security testing + + +#### Additional Regions Available Upon Request + +Auth0 can validate and deploy Private Cloud in additional Azure regions to meet your data residency requirements. Azure region validation is more complex than AWS and requires additional time for thorough testing. + +**Validation process:** +- **Timeline:** Typically 2-8 weeks depending on region complexity and Azure capacity +- **Complexity factors:** + - Availability zone architecture validation + - GeoHA pairing compatibility + - Azure quota and capacity verification (can vary by region) + - Microsoft coordination for capacity allocation +- **Requirements:** Active Private Cloud contract or purchase order + + + **Azure Regional Complexity:** Azure region validation can encounter challenges including limited availability zone support, capacity constraints, and GeoHA pairing issues. Some regions may not be feasible for Private Cloud deployment due to Azure infrastructure limitations. + + +To request validation for a specific Azure region: +1. Contact your Auth0 Account Executive or Technical Account Manager **early in your sales cycle** +2. Provide your preferred region(s) and timeline requirements +3. Auth0 will assess feasibility, including Azure capacity availability +4. If feasible, validation proceeds with estimated timeline provided +5. Deployment proceeds after successful validation + +For detailed information about the region validation process, see [Private Cloud Region Support](/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support). ### Bursty Traffic diff --git a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support.mdx b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support.mdx new file mode 100644 index 0000000000..26c5f07c02 --- /dev/null +++ b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support.mdx @@ -0,0 +1,216 @@ +--- +description: Understand Auth0 Private Cloud region availability, validation process, and how to request deployment in additional regions. +title: Private Cloud Region Support +--- + +Auth0 Private Cloud can be deployed in multiple cloud regions worldwide on both AWS and Azure. This page explains region availability, the validation process, and how to request deployment in additional regions. + +## Production-Ready Regions + +Production-ready regions have completed Auth0's rigorous validation process and are immediately available for Private Cloud deployment. These regions meet Auth0's standards for high availability, performance, security, and operational support. + +### What Makes a Region Production-Ready? + +All production-ready regions undergo comprehensive validation: + + + Auth0 validates that the region supports deployment across multiple availability zones (AZs) to ensure high availability. + + - **AWS:** Minimum 3 availability zones + - **Azure:** Minimum 3 availability zones with proper architectural support + + + + For customers requiring geographic redundancy, Auth0 validates GeoHA pairing between two regions. + + - Validates network latency between paired regions + - Confirms data replication capabilities + - Tests failover and fallback procedures + + + + Auth0 validates that the region has sufficient capacity for Private Cloud workloads and meets performance benchmarks. + + - Cloud provider quota verification + - Load testing at subscribed RPS levels + - Network throughput validation + + + + Auth0 validates security controls and compliance requirements. + + - Encryption at rest and in transit + - Security monitoring and alerting + - Compliance certifications (where applicable) + + +### Current Production-Ready Regions + +For the complete list of production-ready regions, see: +- [Private Cloud on AWS - Data Center Locations](/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws#data-center-locations) +- [Private Cloud on Azure - Data Center Locations](/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure#data-center-locations) + +## Region Validation Process + +If your data residency requirements include a region not listed as production-ready, Auth0 can validate additional regions as part of your Private Cloud engagement. + +### Validation Timeline + +| Cloud Provider | Typical Timeline | Complexity Factors | +|----------------|------------------|-------------------| +| **AWS** | 1-4 weeks | Straightforward in most regions. Can extend if GeoHA pairing requires validation of second region. | +| **Azure** | 2-8 weeks | More complex due to availability zone architecture, capacity constraints, and GeoHA pairing challenges. Microsoft coordination may be required. | + + + **Important:** Region validation timelines are estimates. Some Azure regions may not be feasible for Private Cloud deployment due to infrastructure limitations, capacity constraints, or unavailable GeoHA pairing options. + + +### What Happens During Validation? + +The validation process ensures production-grade reliability before deployment: + + + + Auth0 assesses whether the requested region meets Private Cloud requirements. + + - Availability zone support + - GeoHA pairing availability (if required) + - Cloud provider capacity and quotas + - Network connectivity and latency + + + + Auth0 provisions test infrastructure in the target region. + + - Multi-AZ deployment + - Network configuration + - Security controls + - Monitoring and alerting + + + + Auth0 runs comprehensive tests to validate the deployment. + + - Functional testing (authentication flows, APIs, etc.) + - Performance testing (RPS capacity, latency) + - High availability testing (AZ failover) + - GeoHA testing (if applicable) + + + + Once validation is complete, the region is approved for production use. + + - Customer environment provisioning begins + - Region added to production-ready list (for future customers) + + + +### Known Challenges + +#### Azure Region Complexity + +Azure regions require more extensive validation due to architectural complexity: + +- **Availability Zone Support:** Not all Azure regions support the 3-AZ architecture required for Private Cloud +- **Capacity Constraints:** Azure may have capacity limitations in certain regions, requiring Microsoft coordination to allocate resources +- **GeoHA Pairing Issues:** Some Azure region pairs have incompatible architectures or unsupported configurations + +**Example:** Azure South Africa validation encountered architectural challenges that made GeoHA deployment infeasible, requiring the customer to pivot to Azure Europe. + +#### GeoHA Pairing Validation + +If your deployment requires GeoHA, Auth0 must validate **both** regions and the pairing between them: + +- Doubles validation timeline (both regions must be validated) +- Requires compatible architectures in both regions +- Network latency between regions must meet requirements + +### Cost Considerations + +**No additional cost for standard region validation.** Region validation is included as part of your Private Cloud engagement when: +- You have an active Private Cloud contract or purchase order +- Validation occurs during your onboarding window + +**Infrastructure changes may incur costs.** If validation reveals infrastructure limitations requiring custom solutions, Auth0 will provide a cost estimate before proceeding. + +## Requesting Region Validation + +To request validation for a region not listed as production-ready: + +### 1. Contact Auth0 During Sales Cycle + + + **Best Practice:** Discuss region requirements with your Auth0 Account Executive **before** contract signing to ensure validation can complete before your deployment timeline. + + +Provide the following information: +- **Primary region:** Your preferred deployment region +- **Secondary region:** (If GeoHA required) Your preferred failover region +- **Timeline:** When you need the environment ready for production +- **Business context:** Data residency requirements, compliance needs, proximity to users + +### 2. Auth0 Feasibility Assessment + +Auth0 will assess feasibility within 5 business days: +- Region architecture review +- Capacity and quota check with cloud provider +- GeoHA pairing validation (if applicable) +- Estimated validation timeline + +**Possible outcomes:** +- ✅ **Feasible:** Validation can proceed with estimated timeline +- ⚠️ **Feasible with caveats:** Validation possible but may encounter challenges +- ❌ **Not feasible:** Region cannot support Private Cloud requirements (Auth0 will recommend alternatives) + +### 3. Validation Execution + +If feasible, Auth0 begins validation: +- Validation can run in parallel with contract finalization +- Auth0 provides weekly status updates +- Any blockers are escalated immediately + +### 4. Production Deployment + +After successful validation: +- Your Private Cloud environment is provisioned in the validated region +- Onboarding proceeds according to standard timeline +- Region is added to production-ready list for future customers + +## Frequently Asked Questions + + + Yes, but the region must be validated first. Contact your Auth0 Account Executive early in your sales cycle to request validation. + + + + - **AWS:** Typically 1-4 weeks + - **Azure:** Typically 2-8 weeks + + GeoHA deployments require validation of both regions, which extends the timeline. + + + + Auth0 will work with you to identify alternative regions that meet your data residency requirements. In most cases, nearby regions in the same geography are viable alternatives. + + + + No, standard region validation is included with your Private Cloud engagement. Custom infrastructure requirements may incur additional costs, which Auth0 will discuss upfront. + + + + Yes, but it may delay your production deployment timeline. Auth0 strongly recommends requesting validation during your sales cycle to ensure the region is ready when you need it. + + + + Azure regions have more variability in architecture, capacity, and availability zone support. Some Azure regions also have GeoHA pairing challenges that require extensive coordination with Microsoft. + + + + Auth0 will work with the cloud provider to resolve issues when possible. If issues cannot be resolved, Auth0 will recommend alternative regions and restart validation if needed. + + +## Contact + +For region validation requests or questions about region availability: +- **Sales inquiries:** [Contact Auth0 Sales](https://auth0.com/contact-us) +- **Existing customers:** Contact your Technical Account Manager or [Support Center](https://support.auth0.com/) From e3fa15c083a22fb4242af2ef43102e2788449b4a Mon Sep 17 00:00:00 2001 From: Nick Gagliardi Date: Fri, 27 Feb 2026 13:41:22 -0500 Subject: [PATCH 2/2] update per pawan request --- .../private-cloud-on-aws.mdx | 64 ++---- .../private-cloud-on-azure.mdx | 59 +---- .../private-cloud-region-support.mdx | 216 ------------------ 3 files changed, 24 insertions(+), 315 deletions(-) delete mode 100644 main/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support.mdx diff --git a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws.mdx b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws.mdx index 47e9e36899..c2e9616fa3 100644 --- a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws.mdx +++ b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws.mdx @@ -116,59 +116,27 @@ Guaranteed requests per second (RPS) and SLA do not apply to non-production envi ### Data Center Locations -Auth0 Private Cloud on AWS is available in multiple regions worldwide. All regions listed below have been validated for production deployment and meet Auth0's high availability and performance standards. +Private Cloud on AWS is fully deployable in the following regions: -#### Production-Ready Regions - -The following AWS regions are **fully validated and production-ready** for immediate deployment: - -* Australia (Sydney) +* Australia * Bahrain -* Brazil (São Paulo) -* Canada (Central) -* France (Paris) -* Germany (Frankfurt) +* Brazil +* Canada +* France +* Germany * Hong Kong -* India (Mumbai, Hyderabad) -* Ireland (Dublin) -* Italy (Milan) -* Japan (Tokyo) -* Mexico (Central) +* India +* Indonesia +* Ireland +* Japan +* Mexico * Singapore -* South Korea (Seoul) -* Sweden (Stockholm) +* South Africa +* South Korea +* Sweden * United Arab Emirates (UAE) -* United Kingdom (London) -* USA (Multiple regions) - - - All production-ready regions have undergone rigorous validation including: - - Multi-availability zone deployment verification - - High availability (GeoHA) pairing validation - - Performance and capacity testing - - Security and compliance review - - -#### Additional Regions Available Upon Request - -Auth0 can validate and deploy Private Cloud in additional AWS regions to meet your data residency requirements. Region validation ensures production-grade reliability and performance before deployment. - -**Validation process:** -- **Timeline:** Typically 1-4 weeks depending on region complexity -- **Scope:** Multi-AZ deployment, capacity verification, GeoHA pairing (if applicable) -- **Requirements:** Active Private Cloud contract or purchase order - -To request validation for a specific AWS region: -1. Contact your Auth0 Account Executive or Technical Account Manager -2. Provide your preferred region(s) and timeline requirements -3. Auth0 will assess feasibility and provide a validation timeline -4. Deployment proceeds after successful validation - - - **Planning Ahead:** Request region validation during your sales cycle to ensure your preferred region is ready for deployment at contract start. Last-minute requests may delay your implementation timeline. - - -For detailed information about the region validation process, see [Private Cloud Region Support](/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support). +* United Kingdom +* USA ### Bursty Traffic diff --git a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure.mdx b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure.mdx index 87582957aa..d3f2a1e94b 100644 --- a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure.mdx +++ b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure.mdx @@ -100,57 +100,14 @@ Guaranteed requests per second (RPS) and SLA do not apply to non-production envi ### Data Center Locations -Auth0 Private Cloud on Azure is available in multiple regions worldwide. All regions listed below have been validated for production deployment and meet Auth0's high availability and performance standards. - -#### Production-Ready Regions - -The following Azure regions are **fully validated and production-ready** for immediate deployment: - -* Australia (East) -* Brazil (South) -* Canada (Central) -* France (Central) -* Germany (West Central) -* Ireland (West Europe) -* Japan (East) -* South Korea (Central) -* Sweden (Central) -* United Kingdom (South) -* USA (Multiple regions) - - - All production-ready regions have undergone rigorous validation including: - - Three availability zone deployment verification - - High availability (GeoHA) pairing validation (if applicable) - - Azure capacity and quota verification - - Performance and security testing - - -#### Additional Regions Available Upon Request - -Auth0 can validate and deploy Private Cloud in additional Azure regions to meet your data residency requirements. Azure region validation is more complex than AWS and requires additional time for thorough testing. - -**Validation process:** -- **Timeline:** Typically 2-8 weeks depending on region complexity and Azure capacity -- **Complexity factors:** - - Availability zone architecture validation - - GeoHA pairing compatibility - - Azure quota and capacity verification (can vary by region) - - Microsoft coordination for capacity allocation -- **Requirements:** Active Private Cloud contract or purchase order - - - **Azure Regional Complexity:** Azure region validation can encounter challenges including limited availability zone support, capacity constraints, and GeoHA pairing issues. Some regions may not be feasible for Private Cloud deployment due to Azure infrastructure limitations. - - -To request validation for a specific Azure region: -1. Contact your Auth0 Account Executive or Technical Account Manager **early in your sales cycle** -2. Provide your preferred region(s) and timeline requirements -3. Auth0 will assess feasibility, including Azure capacity availability -4. If feasible, validation proceeds with estimated timeline provided -5. Deployment proceeds after successful validation - -For detailed information about the region validation process, see [Private Cloud Region Support](/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support). +Private Cloud on Azure is fully deployable in the following regions: + +* Australia +* Canada +* Germany +* Switzerland +* United Kingdom +* USA ### Bursty Traffic diff --git a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support.mdx b/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support.mdx deleted file mode 100644 index 26c5f07c02..0000000000 --- a/main/docs/deploy-monitor/deploy-private-cloud/private-cloud-region-support.mdx +++ /dev/null @@ -1,216 +0,0 @@ ---- -description: Understand Auth0 Private Cloud region availability, validation process, and how to request deployment in additional regions. -title: Private Cloud Region Support ---- - -Auth0 Private Cloud can be deployed in multiple cloud regions worldwide on both AWS and Azure. This page explains region availability, the validation process, and how to request deployment in additional regions. - -## Production-Ready Regions - -Production-ready regions have completed Auth0's rigorous validation process and are immediately available for Private Cloud deployment. These regions meet Auth0's standards for high availability, performance, security, and operational support. - -### What Makes a Region Production-Ready? - -All production-ready regions undergo comprehensive validation: - - - Auth0 validates that the region supports deployment across multiple availability zones (AZs) to ensure high availability. - - - **AWS:** Minimum 3 availability zones - - **Azure:** Minimum 3 availability zones with proper architectural support - - - - For customers requiring geographic redundancy, Auth0 validates GeoHA pairing between two regions. - - - Validates network latency between paired regions - - Confirms data replication capabilities - - Tests failover and fallback procedures - - - - Auth0 validates that the region has sufficient capacity for Private Cloud workloads and meets performance benchmarks. - - - Cloud provider quota verification - - Load testing at subscribed RPS levels - - Network throughput validation - - - - Auth0 validates security controls and compliance requirements. - - - Encryption at rest and in transit - - Security monitoring and alerting - - Compliance certifications (where applicable) - - -### Current Production-Ready Regions - -For the complete list of production-ready regions, see: -- [Private Cloud on AWS - Data Center Locations](/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-aws#data-center-locations) -- [Private Cloud on Azure - Data Center Locations](/docs/deploy-monitor/deploy-private-cloud/private-cloud-on-azure#data-center-locations) - -## Region Validation Process - -If your data residency requirements include a region not listed as production-ready, Auth0 can validate additional regions as part of your Private Cloud engagement. - -### Validation Timeline - -| Cloud Provider | Typical Timeline | Complexity Factors | -|----------------|------------------|-------------------| -| **AWS** | 1-4 weeks | Straightforward in most regions. Can extend if GeoHA pairing requires validation of second region. | -| **Azure** | 2-8 weeks | More complex due to availability zone architecture, capacity constraints, and GeoHA pairing challenges. Microsoft coordination may be required. | - - - **Important:** Region validation timelines are estimates. Some Azure regions may not be feasible for Private Cloud deployment due to infrastructure limitations, capacity constraints, or unavailable GeoHA pairing options. - - -### What Happens During Validation? - -The validation process ensures production-grade reliability before deployment: - - - - Auth0 assesses whether the requested region meets Private Cloud requirements. - - - Availability zone support - - GeoHA pairing availability (if required) - - Cloud provider capacity and quotas - - Network connectivity and latency - - - - Auth0 provisions test infrastructure in the target region. - - - Multi-AZ deployment - - Network configuration - - Security controls - - Monitoring and alerting - - - - Auth0 runs comprehensive tests to validate the deployment. - - - Functional testing (authentication flows, APIs, etc.) - - Performance testing (RPS capacity, latency) - - High availability testing (AZ failover) - - GeoHA testing (if applicable) - - - - Once validation is complete, the region is approved for production use. - - - Customer environment provisioning begins - - Region added to production-ready list (for future customers) - - - -### Known Challenges - -#### Azure Region Complexity - -Azure regions require more extensive validation due to architectural complexity: - -- **Availability Zone Support:** Not all Azure regions support the 3-AZ architecture required for Private Cloud -- **Capacity Constraints:** Azure may have capacity limitations in certain regions, requiring Microsoft coordination to allocate resources -- **GeoHA Pairing Issues:** Some Azure region pairs have incompatible architectures or unsupported configurations - -**Example:** Azure South Africa validation encountered architectural challenges that made GeoHA deployment infeasible, requiring the customer to pivot to Azure Europe. - -#### GeoHA Pairing Validation - -If your deployment requires GeoHA, Auth0 must validate **both** regions and the pairing between them: - -- Doubles validation timeline (both regions must be validated) -- Requires compatible architectures in both regions -- Network latency between regions must meet requirements - -### Cost Considerations - -**No additional cost for standard region validation.** Region validation is included as part of your Private Cloud engagement when: -- You have an active Private Cloud contract or purchase order -- Validation occurs during your onboarding window - -**Infrastructure changes may incur costs.** If validation reveals infrastructure limitations requiring custom solutions, Auth0 will provide a cost estimate before proceeding. - -## Requesting Region Validation - -To request validation for a region not listed as production-ready: - -### 1. Contact Auth0 During Sales Cycle - - - **Best Practice:** Discuss region requirements with your Auth0 Account Executive **before** contract signing to ensure validation can complete before your deployment timeline. - - -Provide the following information: -- **Primary region:** Your preferred deployment region -- **Secondary region:** (If GeoHA required) Your preferred failover region -- **Timeline:** When you need the environment ready for production -- **Business context:** Data residency requirements, compliance needs, proximity to users - -### 2. Auth0 Feasibility Assessment - -Auth0 will assess feasibility within 5 business days: -- Region architecture review -- Capacity and quota check with cloud provider -- GeoHA pairing validation (if applicable) -- Estimated validation timeline - -**Possible outcomes:** -- ✅ **Feasible:** Validation can proceed with estimated timeline -- ⚠️ **Feasible with caveats:** Validation possible but may encounter challenges -- ❌ **Not feasible:** Region cannot support Private Cloud requirements (Auth0 will recommend alternatives) - -### 3. Validation Execution - -If feasible, Auth0 begins validation: -- Validation can run in parallel with contract finalization -- Auth0 provides weekly status updates -- Any blockers are escalated immediately - -### 4. Production Deployment - -After successful validation: -- Your Private Cloud environment is provisioned in the validated region -- Onboarding proceeds according to standard timeline -- Region is added to production-ready list for future customers - -## Frequently Asked Questions - - - Yes, but the region must be validated first. Contact your Auth0 Account Executive early in your sales cycle to request validation. - - - - - **AWS:** Typically 1-4 weeks - - **Azure:** Typically 2-8 weeks - - GeoHA deployments require validation of both regions, which extends the timeline. - - - - Auth0 will work with you to identify alternative regions that meet your data residency requirements. In most cases, nearby regions in the same geography are viable alternatives. - - - - No, standard region validation is included with your Private Cloud engagement. Custom infrastructure requirements may incur additional costs, which Auth0 will discuss upfront. - - - - Yes, but it may delay your production deployment timeline. Auth0 strongly recommends requesting validation during your sales cycle to ensure the region is ready when you need it. - - - - Azure regions have more variability in architecture, capacity, and availability zone support. Some Azure regions also have GeoHA pairing challenges that require extensive coordination with Microsoft. - - - - Auth0 will work with the cloud provider to resolve issues when possible. If issues cannot be resolved, Auth0 will recommend alternative regions and restart validation if needed. - - -## Contact - -For region validation requests or questions about region availability: -- **Sales inquiries:** [Contact Auth0 Sales](https://auth0.com/contact-us) -- **Existing customers:** Contact your Technical Account Manager or [Support Center](https://support.auth0.com/)