[AutoPublish] main to live - 06/10 14:16 PDT | 06/11 02:46 IST#1185
Conversation
Co-authored-by: Gary Moore <5432776+garycentric@users.noreply.github.com>
Updated the date for the Practitioners Calls Archive and added a new entry for the May 2026 call on the Frontier Firm maturity model. Co-authored-by: Aditi Srivastava <133841950+aditisrivastava07@users.noreply.github.com>
|
Learn Build status updates of commit 3d9f0e9: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@VesaJuvonen Before this PR can be merged, a Content Lead needs to add the Sign off label to it. Only one of the listed reviewers needs to add the Sign off label. Before you sign off a PR, confirm the following:
After you've confirmed the above, do the following to sign off:
After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours. If you think you were incorrectly added as a reviewer, have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |

@MicrosoftDocs/marveldocs-pubops
This is an automated pull request to publish changes from the main branch to the live branch. Merging this PR will publish the changes to the live learn.microsoft.com site.
Auto-merge is enabled. The repo will attempt to automatically merge this PR when all required checks pass. If the PR is automatically merged, no further action is required to publish the contents of this PR.
In the event the repo can't automatically merge this PR, the Manual merge required label will be added to the PR. If this happens, complete the following checks before merging this PR:
After you've completed these steps, manually merge the PR.
If you have questions, post a message to https://aka.ms/tcphelp.