Release/azure communication phone numbers 1.5.0 #51808
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add mobile numbers implementation * Update CHANGELOG.md description * Update autorest.md to include public spec * Face spacing on autorest * Update api version on internal client * Update descriptions on README
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
andrewjhopkins
requested review from
Arazan,
whisper6284,
danielortega-msft and
sofiar-msft
as code owners
There was a problem hiding this comment.
Pull Request Overview
This PR releases version 1.5.0 of the Azure Communication Phone Numbers SDK, promoting the mobile number types feature from beta to GA. The release includes support for mobile phone numbers, which are location-associated numbers with SMS capabilities, and updates the default API version to 2025-06-01.
Key changes include:
- Adding mobile phone number support through new overloaded methods for localities and area codes
- Updating the service version from 2025-04-01 to 2025-06-01
- Expanding test coverage for mobile number scenarios
Reviewed Changes
Copilot reviewed 12 out of 19 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| PhoneNumbersReservationsTests.cs | Adds comprehensive test coverage for mobile phone number types in reservation operations |
| PhoneNumbersClientLiveTests.cs | Adds live tests for mobile area codes and localities with phone number type filtering |
| autorest.md | Updates API specification reference from 2025-04-01 to 2025-06-01 |
| PhoneNumbersClientOptions.cs | Adds V2025_06_01 service version and updates default version |
| PhoneNumbersClient.cs | Adds overloaded methods for GetAvailableLocalities and GetAvailableAreaCodesMobile |
| InternalPhoneNumbersRestClient.cs | Updates method signatures to support PhoneNumberType parameter |
| Azure.Communication.PhoneNumbers.csproj | Updates version from 1.5.0-beta.1 to 1.5.0 |
| assets.json | Updates asset tag reference |
| API reference files | Adds Mobile phone number type and new method overloads to public API |
| README.md | Updates documentation to describe three phone number types including Mobile |
| CHANGELOG.md | Documents GA release of mobile number types |
sdk/communication/Azure.Communication.PhoneNumbers/src/PhoneNumbersClientOptions.cs
Outdated
Show resolved
Hide resolved
...n/Azure.Communication.PhoneNumbers/tests/PhoneNumbersClient/PhoneNumbersReservationsTests.cs
Show resolved
Hide resolved
...n/Azure.Communication.PhoneNumbers/tests/PhoneNumbersClient/PhoneNumbersReservationsTests.cs
Show resolved
Hide resolved
whisper6284
approved these changes
Aug 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.