-
Notifications
You must be signed in to change notification settings - Fork 21.9k
Update using-expressroute-for-microsoft-pstn.md #127484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Removed eol offerings, small edits for clarity.
|
Learn Build status updates of commit 50ec352: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@slocoach Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks! #label:"aq-pr-triaged" |
|
@microsoft-github-policy-service agree company="Microsoft" |
|
@slocoach : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
@microsoft-github-policy-service agree company="Microsoft" |
@microsoft-github-policy-service agree company="Microsoft" |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
@tracsman Could you review this proposed update to your article and enter Thanks! |
|
Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates documentation for using ExpressRoute with Microsoft PSTN services, removing end-of-life offerings and making editorial improvements for clarity. The changes streamline the content to focus on currently supported services.
- Removed references to deprecated Azure Communications Gateway and Azure Communication Services Direct Routing
- Updated encryption support messaging and service provider recommendations
- Added specific community reference information for configuration
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| --- | ||
| title: 'Using ExpressRoute for Microsoft PSTN Services' | ||
| description: ExpressRoute circuits can be used for Microsoft PSTN services, including Operator Connect, Azure Communications Gateway, and Azure Communication Services Direct Routing. | ||
| description: ExpressRoute circuits can be used for Microsoft PSTN service, Operator Connect. |
Copilot
AI
Oct 2, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description should use 'services' (plural) instead of 'service' (singular) to maintain grammatical consistency, even though only one service is now listed.
| description: ExpressRoute circuits can be used for Microsoft PSTN service, Operator Connect. | |
| description: ExpressRoute circuits can be used for Microsoft PSTN services, Operator Connect. |
| For more information about ExpressRoute, see the [Introduction to ExpressRoute][ExR-Intro] article. | ||
|
|
||
| You can use ExpressRoute Microsoft Peering to connect to the following Microsoft PSTN services: | ||
| You can use ExpressRoute Microsoft Peering to offer the following Microsoft PSTN services: |
Copilot
AI
Oct 2, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The word 'offer' should be 'access' or 'connect to' since customers use ExpressRoute to connect to services, not offer them.
| You can use ExpressRoute Microsoft Peering to offer the following Microsoft PSTN services: | |
| You can use ExpressRoute Microsoft Peering to access the following Microsoft PSTN services: |
|
|
||
| > [!IMPORTANT] | ||
| > Operator Connect SIP Trunks do not support encryption when using ExpressRoute Microsoft Peering connectivity. | ||
| > Encryption support is pending delivery for Express Route PSTN connectivity. |
Copilot
AI
Oct 2, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be 'ExpressRoute' (one word) instead of 'Express Route' (two words) to match the correct product name used throughout the document.
| > Encryption support is pending delivery for Express Route PSTN connectivity. | |
| > Encryption support is pending delivery for ExpressRoute PSTN connectivity. |
Removed eol offerings, small edits for clarity.