MicrosoftDocs
Update about-virtual-hub-routing.md
Updating this document to avoid acrolinux issue and also ensure Cx does not use CAs in Static Route
@MSFT-FrankLpnsk : Thanks for your contribution! The author(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit b71b190:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/virtual-wan/about-virtual-hub-routing.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
PRMerger Results
| Issue | Description |
|---|---|
| File Change Percent | This PR contains file(s) with more than 30% file change. |
@cherylmc Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @cherylmc
@MSFT-FrankLpnsk - You might not have realized that you raised this PR in the public repo rather than the public repo as you usually do. To avoid requiring review from the article's author, please move these changes to the private repo.
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
