Can Azure Communication Services check availability of specific vanity 712 phone numbers?

Question

Can Azure Communication Services check availability of specific vanity 712 phone numbers?

Me to You 0

We are setting up Azure Communication Services calling for a small healthcare practice in Iowa. We contacted the ACS telephone-number team on July 14, July 20, and July 23, 2026, but have not received an availability decision.

We need to know whether Microsoft can search for, specially order, reserve, or support porting of these exact numbers:

Primary voice: 712-934-3278 (712-WE-HEAR-U)
Preferred companion number: 712-329-4968 (712-FAX-4YOU)
Alternate companion number: 712-329-2273 (712-FAX-CARE)

The companion number would ultimately be used with a separate HIPAA-capable fax provider if permitted; the immediate question is whether the exact numbers can be obtained or ported.

Could someone please confirm:

Whether any of these exact numbers are available or can be specially ordered.
The official ACS route for an exact-number or vanity-number availability request.
If exact ordering is unavailable, whether an existing number such as 712-560-1919 can be ported into ACS and what ownership or LOA documentation would be required.
The expected processing timeframe and any one-time or monthly charges.

Our Azure support request was redirected to Microsoft Q&A under the Developer support plan. Please provide the answer here and, if follow-up is needed, contact us by email through our Microsoft profile rather than by phone because I am with patients most of the workday.

No patient information or PHI is involved in this request.

Golla Venkata Pavani 6,525 Reputation points Microsoft External Staff Moderator

2026-07-28T02:31:46.9233333+00:00
Hi @Me to You

Thank you for reaching us regarding the issue.

Can ACS determine whether these exact vanity numbers are available or specially ordered?

Azure Communication Services (ACS) supports a Special** **Order process for telephone numbers when the desired number is not available through the standard Azure portal acquisition workflow. Microsoft documentation states that customers interested in acquiring specific numbers, specific area codes, or numbers that require manual acquisition can submit a special telephone number request. However, the documentation does not provide a public mechanism to check the live availability of a specific telephone number, nor does it guarantee that a requested vanity number can be obtained. Availability is determined during the special-order review process.

Therefore, based on published Microsoft documentation, we cannot confirm whether 712-934-3278 (712-WE-HEAR-U), 712-329-4968 (712-FAX-4YOU), 712-329-2273 (712-FAX-CARE) are currently available, reservable, or obtainable.

What is the official ACS process for requesting an exact or vanity number?

Microsoft documentation identifies the Special** **Order process as the supported route for acquiring numbers that require manual handling. The ACS phone-number documentation instructs customers to:

Open a Special Order request.

Select Azure** Communication **Service as the customer profile.

Select New** TN **Acquisition as the case type.

Submit the required details for review.

Microsoft's ACS special-order guidance further states that customers seeking specific numbers or manually acquired numbers should follow the special-order process and submit the required request form for review.

Can an existing number such as 712-560-1919 be ported into ACS?

Yes. Microsoft documentation states that U.S.** geographic numbers and toll-free numbers are eligible for porting into Azure Communication **Services. To initiate a port request, customers need:

An Azure subscription.

An active ACS resource.

The Azure Resource ID and Immutable Resource ID of the target ACS resource.

The required porting documentation, including a Letter of Authorization (LOA)

Processing timelines and charges

Not Guaranteed turnaround times for special-order or port-in requests

One-time acquisition fees specific to vanity or exact-number requests

Published standard charges that apply once a number is acquired:

U.S. geographic (local) number: USD 1.00 per month leasing fee

U.S. toll-free number: USD 2.00 per month leasing fee

Plus standard pay-as-you-go calling usage charges

Special-order and port requests are handled through the ACS telephone-number workflow. The team provides status updates after a formal submission is received.

Please submit (or re-submit) a formal Special Order request through the Azure portal or to [acstns@microsoft.com] for the three vanity numbers, and/or a Port-In request for any number already under your control. The ACS Telephone Number Services team is the authoritative channel for a definitive availability decision.

No patient information or PHI is required or appropriate for these requests. We will continue to monitor for any response from the telephone-number team and will update you by email as requested.

Reference:
https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/telephony/get-phone-number?tabs=windows&pivots=platform-azp-new
https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/telephony/port-phone-number
https://learn.microsoft.com/en-us/azure/communication-services/concepts/pstn-pricing#united-states-telephony-offers
Kindly let us know if the above helps or you need further assistance on this issue.

Please "accept" if the information helped you. This will help us and others in the community as well.
Golla Venkata Pavani 6,525 Reputation points Microsoft External Staff Moderator

2026-08-02T13:09:33.3833333+00:00

Hi @Me to You

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

1 answer

Your answer

Golla Venkata Pavani 6,525 Reputation points Microsoft External Staff Moderator

2026-08-02T13:09:33.3833333+00:00

Hi @Me to You

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

Answer 1

Hello Me to You,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to know if Azure Communication Services check availability of specific vanity 712 phone numbers.

For you to be able to check user availability before initiating or routing communication through Azure Communication Services. Understand this that Azure Communication Services does not expose Microsoft Teams or Microsoft 365 user presence/availability APIs. Base on ACS designed, Teams user presence is exposed through Microsoft Graph Presence APIs, not ACS. - https://learn.microsoft.com/en-us/azure/communication-services/overview, https://learn.microsoft.com/en-us/graph/api/resources/presence?view=graph-rest-1.0 This is not an Azure platform defect. It is a product-boundary issue and does not require Azure Support. As a solution architect and base on your scenario, what you can do is to:

Use Microsoft Graph Presence API to check the target Microsoft 365/Teams user’s availability.
Use the Microsoft Entra user object ID, not the ACS communication user ID.
Evaluate the returned availability and activity.
Proceed with ACS calling, chat, SMS, email, or routing only after the presence decision is made.
Use Azure Support only if the validated Graph implementation fails with service-side errors after permissions, consent, user ID, and throttling have been confirmed.

Therefore:

For a single user, call: GET https://graph.microsoft.com/v1.0/users/{user-id}/presence Authorization: Bearer {access_token}
For multiple users, call: POST https://graph.microsoft.com/v1.0/communications/getPresencesByUserId Authorization: Bearer {access_token} Content-Type: application/json { "ids": [ "fa8bf3dc-eca7-46b7-bad1-db199b62afc3", "66825e03-7ef5-42da-9069-724602c31f6b" ] }
Use the response to decide the ACS action: { "id": "66825e03-7ef5-42da-9069-724602c31f6b", "availability": "DoNotDisturb", "activity": "Presenting" }

If the user is Available, proceed with the ACS interaction. If the user is Busy, DoNotDisturb, Away, Offline, or PresenceUnknown, route to another agent, queue the request, send a notification, or schedule a callback based on your business rule. Microsoft Graph documents the presence object as containing the user’s availability and activity, and the get presence endpoint returns that object when the request is authorized. - https://learn.microsoft.com/en-us/graph/api/presence-get?view=graph-rest-1.0, https://learn.microsoft.com/en-us/graph/api/resources/presence?view=graph-rest-1.0

NB-FOR CLARIFICATION:

ACS can be used to call public numbers, but ACS cannot reliably pre-check real-time availability of those public numbers before calling. For Teams users, use Graph Presence. For public PSTN numbers, use ACS PSTN calling and evaluate the call outcome.

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.