An Azure communication platform for deploying applications across devices and platforms.
Hello @Jaymin Kavaiya
The 30 messages/minute and 100 messages/hour limits you're seeing are the current default sending limits for Azure Communication Services Email when using a custom domain. Microsoft confirms that these limits can be increased, but higher quotas are available only for verified custom domains, not Azure-managed domains.
Since you've already configured SPF/DKIM and submitted a request, I would first confirm that the quota request was created under the correct support category. The documented path is:
Azure Portal → Help + support → Create a support request → Service and subscription limits (quotas) → Azure Communication Services Email: Sending Limits
Microsoft has documented this same procedure for ACS Email quota requests.
When submitting the request, include the following information:
- Subscription ID
- Azure Communication Services resource name
- Verified custom sending domain
- Region
- Type of messages being sent - for example, transactional or nonprofit/member communications
- Required maximum messages per minute, per hour, and per day
- Expected peak and normal sending volumes
- Description of your organization and business use case
- Confirmation of how bounced/invalid recipients are handled
Microsoft also evaluates the sender's reputation when considering an increase. This includes delivery failures, domain reputation, spam/abuse reports, and whether the domain has established legitimate sending history. Microsoft's current quota guidance states that email failure rates need to remain low for higher quotas to be approved.
I would not create multiple quota requests if you already have an active case. Since Support said they couldn't locate data associated with the original request, reply to that case with the Subscription ID, ACS resource name (dfw-email-service), Email Communication Service resource, custom domain, region, and original support request ID, and ask them to confirm that the case has been routed specifically to the Azure Communication Services Email quota/sending-limits team.
Also note that quota increases aren't immediate. Microsoft states that requests can take up to 72 hours for evaluation and approval, and approval isn't guaranteed because they review sender reputation and the requested workload.
Your nonprofit use case doesn't prevent you from requesting higher throughput; the key factors are a verified custom domain, clear documentation of the required volume, and demonstrated healthy sending practices.
Sharing these references with you:
Microsoft – ACS Email quota increase process
Microsoft – Azure Communication Services service limits
If Support still can't associate the quota request with the resource after you provide those details, I'd ask them to re-route/escalate the existing case rather than opening another duplicate ticket.
Please "Accept the Answer" if this information helped you. This will help us and others in the community.
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.