Skip to content

Add Practitioners Calls Archive with PDF resources#1148

Merged
Ruchika-mittal01 merged 2 commits intoMicrosoftDocs:mainfrom
mrsbeata:pr3
Jan 20, 2026
Merged

Add Practitioners Calls Archive with PDF resources#1148
Ruchika-mittal01 merged 2 commits intoMicrosoftDocs:mainfrom
mrsbeata:pr3

Conversation

@mrsbeata
Copy link
Contributor

@mrsbeata mrsbeata commented Jan 15, 2026

PubOps Review Feedback

Category

  • Content fix
  • New article

Related issues

  • None

Contents of the Pull Request

This PR adds a new archive page for the Maturity Model for Microsoft 365 Practitioners Calls, providing the community with a comprehensive historical record of all sessions from March 2021 to November 2025.

New files:

  • practitioners-calls-archive.md — Complete archive of 45+ Practitioners Calls
  • 9 PDF presentation slides in media/practiners-call-archive/2025/

Each archived session includes:

  • Date and topic
  • Speaker information with LinkedIn profiles
  • Detailed summary of key takeaways
  • Links to YouTube recordings
  • Links to presentation materials (PPT/PDF)
  • Related competency tags for easy navigation

Topics covered:
Competency deep-dives (Communications, Business Process, Search, Security), practical scenarios (Copilot adoption, branding, process improvement), workshop guidance, and leadership buy-in strategies.

Guidance

This supports ongoing documentation of the Maturity Model for Microsoft 365 community efforts and provides easy access to historical session materials.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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.

# File Term Line Sev AI Recommendation Class AI Review Details
1 Community\practitioners-calls-archive.md damn 187 2 Replacement required Profanity
DetailsThe term `damn` is used as an intensifier in the phrase 'that's damn hard' to emphasize difficulty. This word is considered inappropriate or unprofessional in business, technical, and documentation contexts, and should be removed or replaced with a neutral alternative such as 'very', 'extremely', or simply omitted.

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 120ecc4:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
Community/practitioners-calls-archive.md ❌Error Details

Community/practitioners-calls-archive.md

  • Line 4, Column 9: [Error: violate-schema] Expected type String, please input String or type compatible with String.
  • Line 4, Column 9: [Warning: unexpected-type] Expected type 'String, Null' but got 'Array'.
  • Line 4, Column 9: [Warning: multiple-values - See documentation] Expected type 'String, Null' but got 'Array'.
  • Line 33, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#practical-scenario-copilot-adoption-level-300' in 'practitioners-calls-archive.md'.
  • Line 34, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#revisiting-the-communications-competency' in 'practitioners-calls-archive.md'.
  • Line 35, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#business-process-search-competency-update' in 'practitioners-calls-archive.md'.
  • Line 36, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#process-improvement-practical-scenario-ama' in 'practitioners-calls-archive.md'.
  • Line 37, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#security-culture' in 'practitioners-calls-archive.md'.
  • Line 38, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#practical-scenario-on-branding' in 'practitioners-calls-archive.md'.
  • Line 39, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#maturity-model-and-ai-agents' in 'practitioners-calls-archive.md'.
  • Line 40, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#how-to-run-a-maturity-model-workshop' in 'practitioners-calls-archive.md'.
  • Line 41, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#getting-leadership-buy-in' in 'practitioners-calls-archive.md'.
  • Line 42, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#ignite-and-maturity' in 'practitioners-calls-archive.md'.
  • Line 43, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#adding-sparkle-to-competency' in 'practitioners-calls-archive.md'.
  • Line 44, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#future-ready---what-do-mature-organizations-do-next' in 'practitioners-calls-archive.md'.
  • Line 45, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#practical-scenario---copilot' in 'practitioners-calls-archive.md'.
  • Line 46, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#revisiting-the-management-of-content-competency' in 'practitioners-calls-archive.md'.
  • Line 47, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#creating-a-mature-employee-experience' in 'practitioners-calls-archive.md'.
  • Line 48, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#practical-application---power-platform-coe' in 'practitioners-calls-archive.md'.
  • Line 49, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#revisit-staff--training-and-people--communities' in 'practitioners-calls-archive.md'.
  • Line 50, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#practical-scenarios-service-management' in 'practitioners-calls-archive.md'.
  • Line 51, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#cognitive-business--copilot' in 'practitioners-calls-archive.md'.
  • Line 52, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#case-studies' in 'practitioners-calls-archive.md'.
  • Line 53, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#practical-scenario---sharepoint-syntex' in 'practitioners-calls-archive.md'.
  • Line 54, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#accessibility' in 'practitioners-calls-archive.md'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit f678686:

⚠️ Validation status: warnings

File Status Preview URL Details
Community/practitioners-calls-archive.md ⚠️Warning View Details
Community/media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf ✅Succeeded

Community/practitioners-calls-archive.md

  • Line 35, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#business-process-search-competency-update' in 'practitioners-calls-archive.md', did you mean '#business-process--search-competency-update'?
  • Line 36, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#process-improvement-practical-scenario-ama' in 'practitioners-calls-archive.md', did you mean '#process-improvement-practical-scenario---ama'?
  • Line 72, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#advanced-content-management--retention--compliance' in 'practitioners-calls-archive.md', did you mean '#advanced-content-management-â-retention--compliance'?
  • Line 85, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pptx'.
  • Line 85, Column 153: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-11-18%20-%20Practical%20Scenario%20Copilot%20Adoption%20Level%20300.pdf' will not be built because it is not included in build scope.
  • Line 103, Column 24: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pptx'.
  • Line 103, Column 143: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-10-21%20-%20Revisiting%20the%20Communications%20Competency.pdf' will not be built because it is not included in build scope.
  • Line 121, Column 26: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pptx'.
  • Line 121, Column 154: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-09-16%20-%20Business%20Process%20%26%20Search%20Competency%20Update.pdf' will not be built because it is not included in build scope.
  • Line 139, Column 21: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-06-17%20-%20Process%20Improvement%20Practical%20Scenario%20%20-%20AMA.pdf' will not be built because it is not included in build scope.
  • Line 157, Column 20: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-05-20 - Security Culture.pptx'.
  • Line 157, Column 111: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-05-20%20-%20Security%20Culture.pdf' will not be built because it is not included in build scope.
  • Line 177, Column 22: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pptx'.
  • Line 177, Column 131: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-04-15%20-%20Practical%20Scenario%20on%20Branding.pdf' will not be built because it is not included in build scope.
  • Line 195, Column 22: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pptx'.
  • Line 195, Column 131: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-03-18%20-%20Maturity%20Model%20and%20AI%20Agents.pdf' will not be built because it is not included in build scope.
  • Line 209, Column 25: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-02-18%20-%20How%20to%20run%20a%20Maturity%20Model%20Workshop.pdf' will not be built because it is not included in build scope.
  • Line 225, Column 24: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-01-21%20-%20Getting%20Leadership%20Buy%20In.pdf' will not be built because it is not included in build scope.
  • Line 243, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-12-17 - Ignite and Maturity.pptx'.
  • Line 243, Column 121: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-12-17 - Ignite and Maturity.pdf'.
  • Line 255, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-11-19 - Adding sparkle to Competency.pptx'.
  • Line 255, Column 132: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-11-19 - Adding sparkle to Competency.pdf'.
  • Line 267, Column 24: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-10-15 - Future-Ready - What do mature organizations do next.pptx'.
  • Line 279, Column 26: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-09-17 - Practical Scenario - Copilot.pptx'.
  • Line 291, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-06-18 - Revisiting the Management of Content Competency.pptx'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@github-actions github-actions bot requested a review from VesaJuvonen January 16, 2026 08:31
@github-actions
Copy link

@VesaJuvonen
You've been added as a reviewer to this pull request because you're listed as a Content Lead for the product area or feature covered by one or more articles in this PR.

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:

  • Article content has been checked for technical accuracy.
  • There are no errors or warnings in build validation.
  • There are no severity 1 or 2 PoliCheck issues.
  • All articles have a minimum Acrolinx score of 80.
  • All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

  1. Select the gear next to Labels.
  2. Select Sign off from the label list.
  3. Click away from the label list.

image

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
the PR to the submitter with required changes. After they've completed those changes, you need to sign off again.

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.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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.

# File Term Line Sev AI Recommendation Class AI Review Details
1 Community\practitioners-calls-archive.md damn 187 2 Replacement required Profanity
DetailsThe term `damn` is used as an intensifier in the phrase 'that's damn hard' to emphasize difficulty. This is considered inappropriate language in professional or technical documentation and should be removed or replaced with a neutral alternative such as 'very' or 'extremely'.

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit dcbb79a:

⚠️ Validation status: warnings

File Status Preview URL Details
Community/practitioners-calls-archive.md ⚠️Warning View Details
Community/media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf ✅Succeeded

Community/practitioners-calls-archive.md

  • Line 35, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#business-process-search-competency-update' in 'practitioners-calls-archive.md', did you mean '#business-process--search-competency-update'?
  • Line 36, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#process-improvement-practical-scenario-ama' in 'practitioners-calls-archive.md', did you mean '#process-improvement-practical-scenario---ama'?
  • Line 72, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#advanced-content-management--retention--compliance' in 'practitioners-calls-archive.md', did you mean '#advanced-content-management-â-retention--compliance'?
  • Line 85, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pptx'.
  • Line 85, Column 153: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-11-18%20-%20Practical%20Scenario%20Copilot%20Adoption%20Level%20300.pdf' will not be built because it is not included in build scope.
  • Line 103, Column 24: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pptx'.
  • Line 103, Column 143: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-10-21%20-%20Revisiting%20the%20Communications%20Competency.pdf' will not be built because it is not included in build scope.
  • Line 121, Column 26: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pptx'.
  • Line 121, Column 154: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-09-16%20-%20Business%20Process%20%26%20Search%20Competency%20Update.pdf' will not be built because it is not included in build scope.
  • Line 139, Column 21: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-06-17%20-%20Process%20Improvement%20Practical%20Scenario%20%20-%20AMA.pdf' will not be built because it is not included in build scope.
  • Line 157, Column 20: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-05-20 - Security Culture.pptx'.
  • Line 157, Column 111: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-05-20%20-%20Security%20Culture.pdf' will not be built because it is not included in build scope.
  • Line 177, Column 22: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pptx'.
  • Line 177, Column 131: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-04-15%20-%20Practical%20Scenario%20on%20Branding.pdf' will not be built because it is not included in build scope.
  • Line 195, Column 22: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pptx'.
  • Line 195, Column 131: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-03-18%20-%20Maturity%20Model%20and%20AI%20Agents.pdf' will not be built because it is not included in build scope.
  • Line 209, Column 25: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-02-18%20-%20How%20to%20run%20a%20Maturity%20Model%20Workshop.pdf' will not be built because it is not included in build scope.
  • Line 225, Column 24: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-01-21%20-%20Getting%20Leadership%20Buy%20In.pdf' will not be built because it is not included in build scope.
  • Line 243, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-12-17 - Ignite and Maturity.pptx'.
  • Line 243, Column 121: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-12-17 - Ignite and Maturity.pdf'.
  • Line 255, Column 25: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-11-19 - Adding sparkle to Competency.pptx'.
  • Line 255, Column 132: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-11-19 - Adding sparkle to Competency.pdf'.
  • Line 267, Column 24: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-10-15 - Future-Ready - What do mature organizations do next.pptx'.
  • Line 279, Column 26: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-09-17 - Practical Scenario - Copilot.pptx'.
  • Line 291, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'media/community-calls/2024/Practitioners 2024-06-18 - Revisiting the Management of Content Competency.pptx'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@mrsbeata
Copy link
Contributor Author

@sympmarc - help! I don't know what to fix now. I can't access the link to "PR has no warnings or errors".

@sympmarc
Copy link
Collaborator

@mrsbeata = You've got a list of issues above. Each issue tells you the file and line number where the issue exists. If I'm editing in VS Code, I fix the problem in the file and do another commit. Then the tests run again. I do that until I've solved all the issues.

Some of the links above are internal to Microsoft, so we can't access them. Annoying, but the way it is..

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 699e83e:

⚠️ Validation status: warnings

File Status Preview URL Details
Community/practitioners-calls-archive.md ⚠️Warning View Details
Community/media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf ✅Succeeded

Community/practitioners-calls-archive.md

  • Line 85, Column 25: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-11-18%20-%20Practical%20Scenario%20Copilot%20Adoption%20Level%20300.pdf' will not be built because it is not included in build scope.
  • Line 103, Column 24: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-10-21%20-%20Revisiting%20the%20Communications%20Competency.pdf' will not be built because it is not included in build scope.
  • Line 121, Column 26: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-09-16%20-%20Business%20Process%20%26%20Search%20Competency%20Update.pdf' will not be built because it is not included in build scope.
  • Line 139, Column 21: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-06-17%20-%20Process%20Improvement%20Practical%20Scenario%20%20-%20AMA.pdf' will not be built because it is not included in build scope.
  • Line 157, Column 20: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-05-20%20-%20Security%20Culture.pdf' will not be built because it is not included in build scope.
  • Line 177, Column 22: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-04-15%20-%20Practical%20Scenario%20on%20Branding.pdf' will not be built because it is not included in build scope.
  • Line 195, Column 22: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-03-18%20-%20Maturity%20Model%20and%20AI%20Agents.pdf' will not be built because it is not included in build scope.
  • Line 209, Column 25: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-02-18%20-%20How%20to%20run%20a%20Maturity%20Model%20Workshop.pdf' will not be built because it is not included in build scope.
  • Line 225, Column 24: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-01-21%20-%20Getting%20Leadership%20Buy%20In.pdf' will not be built because it is not included in build scope.
  • Line 8, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'mrsbeata' is not a valid Microsoft alias.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 29e577e:

⚠️ Validation status: warnings

File Status Preview URL Details
Community/practitioners-calls-archive.md ⚠️Warning View Details
Community/media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf ✅Succeeded
Community/media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf ✅Succeeded

Community/practitioners-calls-archive.md

  • Line 85, Column 25: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-11-18%20-%20Practical%20Scenario%20Copilot%20Adoption%20Level%20300.pdf' will not be built because it is not included in build scope.
  • Line 103, Column 24: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-10-21%20-%20Revisiting%20the%20Communications%20Competency.pdf' will not be built because it is not included in build scope.
  • Line 121, Column 26: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-09-16%20-%20Business%20Process%20%26%20Search%20Competency%20Update.pdf' will not be built because it is not included in build scope.
  • Line 139, Column 21: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-06-17%20-%20Process%20Improvement%20Practical%20Scenario%20%20-%20AMA.pdf' will not be built because it is not included in build scope.
  • Line 157, Column 20: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-05-20%20-%20Security%20Culture.pdf' will not be built because it is not included in build scope.
  • Line 177, Column 22: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-04-15%20-%20Practical%20Scenario%20on%20Branding.pdf' will not be built because it is not included in build scope.
  • Line 195, Column 22: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-03-18%20-%20Maturity%20Model%20and%20AI%20Agents.pdf' will not be built because it is not included in build scope.
  • Line 209, Column 25: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-02-18%20-%20How%20to%20run%20a%20Maturity%20Model%20Workshop.pdf' will not be built because it is not included in build scope.
  • Line 225, Column 24: [Warning: link-out-of-scope - See documentation] File 'media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf' referenced by link 'media/practiners-call-archive/2025/Practitioners%202025-01-21%20-%20Getting%20Leadership%20Buy%20In.pdf' will not be built because it is not included in build scope.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

1 similar comment
@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

@mrsbeata
Copy link
Contributor Author

@sympmarc now it's all gone through. I had to remove the PDF files and the PPT files but I will try to add them later. Now I want the archive in place for Tuesday and.. fingers crossed.

@sympmarc
Copy link
Collaborator

@mrsbeata - I'm not sure if you want this pushed to live yet or not. If so, is it good enough to add it into the navigation or should we just let it hide in the background at this point?

@sympmarc sympmarc added the Sign off The pull request is ready to be reviewed and merged by PubOps label Jan 19, 2026
@Ruchika-mittal01 Ruchika-mittal01 self-assigned this Jan 19, 2026
@Ruchika-mittal01 Ruchika-mittal01 added the In review PubOps is reviewing the pull request label Jan 19, 2026
@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

@Ruchika-mittal01
Copy link
Contributor

Hi @mrsbeata,

Following are the blocking issues that need to be resolved before we can merge:

Community/media/practiners-call-archive/2025/Practitioners 2025-01-21 - Getting Leadership Buy In.pdf
Community/media/practiners-call-archive/2025/Practitioners 2025-02-18 - How to run a Maturity Model Workshop.pdf
Community/media/practiners-call-archive/2025/Practitioners 2025-03-18 - Maturity Model and AI Agents.pdf
Community/media/practiners-call-archive/2025/Practitioners 2025-04-15 - Practical Scenario on Branding.pdf
Community/media/practiners-call-archive/2025/Practitioners 2025-05-20 - Security Culture.pdf
Community/media/practiners-call-archive/2025/Practitioners 2025-06-17 - Process Improvement Practical Scenario - AMA.pdf
Community/media/practiners-call-archive/2025/Practitioners 2025-09-16 - Business Process & Search Competency Update.pdf
Community/media/practiners-call-archive/2025/Practitioners 2025-10-21 - Revisiting the Communications Competency.pdf
Community/media/practiners-call-archive/2025/Practitioners 2025-11-18 - Practical Scenario Copilot Adoption Level 300.pdf

  • File names should end either with .md or .yml. No other file types are allowed.
  • File names must use lowercase letters, numbers, and hyphens only, with no spaces or special characters.

Community/practitioners-calls-archive.md

  • Add the newly added content to the TOC or add ROBOTS: NOINDEX, NOFOLLOW in the metadata.
  • Line 19: The alt text for the image is incorrect. It must begin with "Screenshot that shows" or "Diagram of" mentioning the graphic type and end with a period.
  • Replace all [To be added] placeholders with complete content.
  • Line 125: Replace the informal wording “rubbish” with professional terminology.

Reference

Criteria used for pull request reviews

Blocking

  • The following are the only file types that are allowed in Magic repos:
    Private repos: md, yml, ps1, xml, jpg, png, gif, svg, csv
    Public repos: md, yml, jpg, png, gif, svg, csv
    All other file types must be stored elsewhere, such as Microsoft Download Center. For more information about Download Center, see Publish or update a file on the Microsoft Download Center.

  • Names for new files and folders follow these guidelines:
    Use only lowercase letters, hyphens, and numbers. No spaces, underscores, or other special characters. (All file types)
    Maximum length is 80 characters, which is a publishing system limit. (All file types)
    Use action verbs that are specific, such as develop, buy, build, or troubleshoot. Avoid "-ing" words. (Folders and articles)
    Don't use unnecessary small words, such as a, or, and, the, and in. (Folders)
    Exception: Names of files for Microsoft Edge policies and files & folders for PowerShell reference content should match the capitalization of the policies, modules, and cmdlets that they document. It's the contributor's responsibility to ensure that these are correct.

  • When a new article is added, the same PR must also contain at least one updated TOC with an entry for the new article. Exceptions are allowed when the file has ROBOTS: NOINDEX, NOFOLLOW in the metadata.

  • Images include alt text.
    Alt text must describe the content of the image adequately.
    Alt text must end with a period.
    Alt text should describe the type of image being used, such as "screenshot" or "diagram."
    Example: "Screenshot that shows how to update a working branch with the main branch in GitHub."

  • Incomplete or placeholder content isn't allowed.

After you resolve the blocking issues, remove the Back to submitter label and add the Sign off label again.

If you need help resolving issues in this PR, post your question in the Trusted Content Teams Channel.

Thanks,
Ruchika

@Ruchika-mittal01 Ruchika-mittal01 added Back to submitter The pull request didn't pass the review criteria and has been returned to the writer for updates PubOps fixes PubOps has fixed some issues in this PR. and removed In review PubOps is reviewing the pull request Sign off The pull request is ready to be reviewed and merged by PubOps labels Jan 20, 2026
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit ea91bc6:

✅ Validation status: passed

File Status Preview URL Details
Community/practitioners-calls-archive.md ✅Succeeded View

For more details, please refer to the build report.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit b387eb4:

✅ Validation status: passed

File Status Preview URL Details
Community/practitioners-calls-archive.md ✅Succeeded View
Community/TOC.yml ✅Succeeded View

For more details, please refer to the build report.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 619a05d:

✅ Validation status: passed

File Status Preview URL Details
Community/practitioners-calls-archive.md ✅Succeeded View
Community/TOC.yml ✅Succeeded View

For more details, please refer to the build report.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@mrsbeata
Copy link
Contributor Author

@Ruchika-mittal01 @sympmarc - I think it's all sorted now.

@sympmarc sympmarc added Sign off The pull request is ready to be reviewed and merged by PubOps and removed Back to submitter The pull request didn't pass the review criteria and has been returned to the writer for updates labels Jan 20, 2026
@Ruchika-mittal01 Ruchika-mittal01 added the In review PubOps is reviewing the pull request label Jan 20, 2026
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit ea9aad0:

✅ Validation status: passed

File Status Preview URL Details
Community/practitioners-calls-archive.md ✅Succeeded View
Community/TOC.yml ✅Succeeded View

For more details, please refer to the build report.

@learn-build-service-prod
Copy link
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@Ruchika-mittal01 Ruchika-mittal01 merged commit 8eaf6c4 into MicrosoftDocs:main Jan 20, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

In review PubOps is reviewing the pull request microsoft-365/svc PubOps fixes PubOps has fixed some issues in this PR. Sign off The pull request is ready to be reviewed and merged by PubOps

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants