Azure Cloud Migration Sizing for 2,000+ Extensions

[Gummies]

Hi everyone,

We are planning to migrate our 3CX PBX (Debian Linux) from an on-premise hypervisor to a public cloud infrastructure (Azure ). Our deployment will serve 2,000+ registered extensions.

Reviewing the official documentation (Recommended Hardware Specifications for 3CX), the bare-metal section specifies Enterprise+ specs (8+ vCPU, 32+ GB RAM, 640+ GB SSD), but the Cloud Provider section only lists recommendations up to the "Large" tier (250 extensions):

• Azure stops at Standard_B4as_v2

Given that burstable CPU instances (T/B series) are unsuitable for large real-time voice workloads due to CPU throttling, could the 3CX team or experienced partners clarify:

1. Specific Cloud Instance Families: What are the benchmarked instance families for 2,000+ extensions (e.g.,Azure D-series v5,?
2. vCPU & RAM Target: Is the 8 vCPU / 32 GB RAM baseline sufficient in a cloud environment at this user scale, or is 16 vCPU / 64 GB RAM strongly advised once CRM integrations, active queues, and call recording are running?
3. Storage & Disk I/O: What baseline IOPS/throughput configuration is recommended for the database and recordings disk (e.g.,Azure Premium SSD)?

Planned Deployment Details:

• Registered Extensions: 2,000+
• Target Platforms under review: Azure VMs
• Concurrent Calls (SC): [512 SC]
• Features: Call queues, recording, WebRTC apps, MS Dynamics CRM integration, Voiptools addon

Thanks for your input

 

[Alejandro_3CX]

Hi @Gummies I can notice you have a partner assigned who can open a support ticket with us, they will need to fill out a questionnaire regarding this deployment so we can advise about the recommended hardware resources.

Please, ask your 3CX Partner to submit this ticket with us, in this way we may review it and advise.

Thank you so much!