Resolve syncing conflicts from repo_sync_working_branch to public

[learn-build-service-prod]

Pull request opened by Docs to resolve syncing conflicts from repo_sync_working_branch to public.

[github-actions]

Caution: Large pull request

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 75 files, which exceeds the warning limit of 30.

Before this pull request can be merged, you must review the list of files it contains and their changes to confirm they are correct and intentional. This includes files you did not change and/or do not own. If there are changes you aren't familiar with, contact the individuals who submitted the commits included in this pull request and review the changes with them.

The individual who merges this pull request is responsible for ensuring the changes included in it are correct, and for resolving any issues that might result in merging it.

To merge this pull request

If you have determined that the changes in this pull request are correct, add the Merge large pull request^* label to it, wait for the max/pr-file-count check to pass, and then click Merge. To add a label, click the gear icon next to Labels and then select Merge large pull request^*.

To reject this pull request

If you can't confirm the changes in this pull request are correct, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit 3bba329:

✅ Validation status: passed

File	Status	Preview URL	Details
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded
Teams/audio-conferencing-dial-out-usage-report.md	✅Succeeded
Teams/cloud-voice-network-settings.md	✅Succeeded
Teams/configure-lobby-sensitive-meetings.md	✅Succeeded
Teams/configure-meetings-baseline-protection.md	✅Succeeded
Teams/configure-meetings-highly-sensitive-protection.md	✅Succeeded
Teams/configure-meetings-three-tiers-protection.md	✅Succeeded
Teams/copilot-teams-transcription.md	✅Succeeded
Teams/cqd-intelligent-media-quality-classifiers.md	✅Succeeded
Teams/CQD-Power-BI-connector.md	✅Succeeded
Teams/customize-meeting-invitations.md	✅Succeeded
Teams/delete-exchange-online-transcripts.md	✅Succeeded
Teams/devices/certified-device-apps.md	✅Succeeded
Teams/devices/certified-devices-overview.md	✅Succeeded
Teams/devices/certified-hardware-android.md	✅Succeeded
Teams/devices/qos-on-teams-devices.md	✅Succeeded
Teams/devices/teams-displays-certified-hardware.md	✅Succeeded
Teams/devices/teams-panels-certified-hardware.md	✅Succeeded
Teams/devices/teams-phones-certified-hardware.md	✅Succeeded
Teams/easy-policy-setup-edu.md	✅Succeeded
Teams/edu-parents-app.md	✅Succeeded
Teams/enhanced-teams-experience.md	✅Succeeded
Teams/includes/m365-teams-resource-account-difference.md	✅Succeeded
Teams/includes/mtr-device-config-account-include.md	✅Succeeded

This comment lists only the first 25 files in the pull request.
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

[github-actions]

Caution: Large pull request

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 77 files, which exceeds the warning limit of 30.

Before this pull request can be merged, you must review the list of files it contains and their changes to confirm they are correct and intentional. This includes files you did not change and/or do not own. If there are changes you aren't familiar with, contact the individuals who submitted the commits included in this pull request and review the changes with them.

The individual who merges this pull request is responsible for ensuring the changes included in it are correct, and for resolving any issues that might result in merging it.

To merge this pull request

If you have determined that the changes in this pull request are correct, add the Merge large pull request^* label to it, wait for the max/pr-file-count check to pass, and then click Merge. To add a label, click the gear icon next to Labels and then select Merge large pull request^*.

To reject this pull request

If you can't confirm the changes in this pull request are correct, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit c1cd3b4:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/teams-administrative-units.md	💡Suggestion		Details
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded
Teams/audio-conferencing-dial-out-usage-report.md	✅Succeeded
Teams/cloud-voice-network-settings.md	✅Succeeded
Teams/configure-lobby-sensitive-meetings.md	✅Succeeded
Teams/configure-meetings-baseline-protection.md	✅Succeeded
Teams/configure-meetings-highly-sensitive-protection.md	✅Succeeded
Teams/configure-meetings-three-tiers-protection.md	✅Succeeded
Teams/copilot-teams-transcription.md	✅Succeeded
Teams/cqd-intelligent-media-quality-classifiers.md	✅Succeeded
Teams/CQD-Power-BI-connector.md	✅Succeeded
Teams/customize-meeting-invitations.md	✅Succeeded
Teams/delete-exchange-online-transcripts.md	✅Succeeded
Teams/devices/certified-device-apps.md	✅Succeeded
Teams/devices/certified-devices-overview.md	✅Succeeded
Teams/devices/certified-hardware-android.md	✅Succeeded
Teams/devices/qos-on-teams-devices.md	✅Succeeded
Teams/devices/teams-displays-certified-hardware.md	✅Succeeded
Teams/devices/teams-panels-certified-hardware.md	✅Succeeded
Teams/devices/teams-phones-certified-hardware.md	✅Succeeded
Teams/easy-policy-setup-edu.md	✅Succeeded
Teams/edu-parents-app.md	✅Succeeded
Teams/enhanced-teams-experience.md	✅Succeeded
Teams/includes/m365-teams-resource-account-difference.md	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions]

Caution: Large pull request

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 77 files, which exceeds the warning limit of 30.

Before this pull request can be merged, you must review the list of files it contains and their changes to confirm they are correct and intentional. This includes files you did not change and/or do not own. If there are changes you aren't familiar with, contact the individuals who submitted the commits included in this pull request and review the changes with them.

The individual who merges this pull request is responsible for ensuring the changes included in it are correct, and for resolving any issues that might result in merging it.

To merge this pull request

If you have determined that the changes in this pull request are correct, add the Merge large pull request^* label to it, wait for the max/pr-file-count check to pass, and then click Merge. To add a label, click the gear icon next to Labels and then select Merge large pull request^*.

To reject this pull request

If you can't confirm the changes in this pull request are correct, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit 6be0f96:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/teams-administrative-units.md	💡Suggestion		Details
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded
Teams/audio-conferencing-dial-out-usage-report.md	✅Succeeded
Teams/cloud-voice-network-settings.md	✅Succeeded
Teams/configure-lobby-sensitive-meetings.md	✅Succeeded
Teams/configure-meetings-baseline-protection.md	✅Succeeded
Teams/configure-meetings-highly-sensitive-protection.md	✅Succeeded
Teams/configure-meetings-three-tiers-protection.md	✅Succeeded
Teams/copilot-teams-transcription.md	✅Succeeded
Teams/cqd-intelligent-media-quality-classifiers.md	✅Succeeded
Teams/CQD-Power-BI-connector.md	✅Succeeded
Teams/customize-meeting-invitations.md	✅Succeeded
Teams/delete-exchange-online-transcripts.md	✅Succeeded
Teams/devices/certified-device-apps.md	✅Succeeded
Teams/devices/certified-devices-overview.md	✅Succeeded
Teams/devices/certified-hardware-android.md	✅Succeeded
Teams/devices/qos-on-teams-devices.md	✅Succeeded
Teams/devices/teams-displays-certified-hardware.md	✅Succeeded
Teams/devices/teams-panels-certified-hardware.md	✅Succeeded
Teams/devices/teams-phones-certified-hardware.md	✅Succeeded
Teams/easy-policy-setup-edu.md	✅Succeeded
Teams/edu-parents-app.md	✅Succeeded
Teams/enhanced-teams-experience.md	✅Succeeded
Teams/includes/m365-teams-resource-account-difference.md	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions]

Caution: Large pull request

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 77 files, which exceeds the warning limit of 30.

Before this pull request can be merged, you must review the list of files it contains and their changes to confirm they are correct and intentional. This includes files you did not change and/or do not own. If there are changes you aren't familiar with, contact the individuals who submitted the commits included in this pull request and review the changes with them.

The individual who merges this pull request is responsible for ensuring the changes included in it are correct, and for resolving any issues that might result in merging it.

To merge this pull request

If you have determined that the changes in this pull request are correct, add the Merge large pull request^* label to it, wait for the max/pr-file-count check to pass, and then click Merge. To add a label, click the gear icon next to Labels and then select Merge large pull request^*.

To reject this pull request

If you can't confirm the changes in this pull request are correct, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit caeda17:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/teams-administrative-units.md	💡Suggestion		Details
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded
Teams/audio-conferencing-dial-out-usage-report.md	✅Succeeded
Teams/cloud-voice-network-settings.md	✅Succeeded
Teams/configure-lobby-sensitive-meetings.md	✅Succeeded
Teams/configure-meetings-baseline-protection.md	✅Succeeded
Teams/configure-meetings-highly-sensitive-protection.md	✅Succeeded
Teams/configure-meetings-three-tiers-protection.md	✅Succeeded
Teams/copilot-teams-transcription.md	✅Succeeded
Teams/cqd-intelligent-media-quality-classifiers.md	✅Succeeded
Teams/CQD-Power-BI-connector.md	✅Succeeded
Teams/customize-meeting-invitations.md	✅Succeeded
Teams/delete-exchange-online-transcripts.md	✅Succeeded
Teams/devices/certified-device-apps.md	✅Succeeded
Teams/devices/certified-devices-overview.md	✅Succeeded
Teams/devices/certified-hardware-android.md	✅Succeeded
Teams/devices/qos-on-teams-devices.md	✅Succeeded
Teams/devices/teams-displays-certified-hardware.md	✅Succeeded
Teams/devices/teams-panels-certified-hardware.md	✅Succeeded
Teams/devices/teams-phones-certified-hardware.md	✅Succeeded
Teams/easy-policy-setup-edu.md	✅Succeeded
Teams/edu-parents-app.md	✅Succeeded
Teams/enhanced-teams-experience.md	✅Succeeded
Teams/includes/m365-teams-resource-account-difference.md	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions]

Too many files - PR blocked

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 154 files, which exceeds the block limit of 100. This PR will not be merged.

To merge this pull request

You must either reduce the number of files being changed to below the 100 file limit or split the changes into multiple PRs. PRs must not have more than 100 files and fewer than 30 files if possible.

To reject this pull request

If you want to abandon these changes and not merge this PR, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit d5abb5c:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/rooms/voice-and-face-recognition.md	💡Suggestion		Details
Teams/teams-administrative-units.md	💡Suggestion		Details
.openpublishing.redirection.json	✅Succeeded
Skype/SfbServer/deploy/deploy-persistent-chat-server/add-persistent-chat-server.md	✅Succeeded
Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-hadr-for-persistent-chat.md	✅Succeeded
Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-server-options.md	✅Succeeded
Skype/SfbServer/deploy/deploy-persistent-chat-server/configure-persistent-chat-user-policies.md	✅Succeeded
Skype/SfbServer/deploy/deploy-persistent-chat-server/create-a-persistent-chat-administrator.md	✅Succeeded
Skype/SfbServer/deploy/deploy-persistent-chat-server/deploy-persistent-chat-server.md	✅Succeeded
Skype/SfbServer/deploy/deploy-persistent-chat-server/install-persistent-chat-components.md	✅Succeeded
Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in-main-page.md	✅Succeeded
Skype/SfbServer/help-topics/help-lscp/persistent-chat-add-in.md	✅Succeeded
Skype/SfbServer/help-topics/help-lscp/persistent-chat-category-main-page.md	✅Succeeded
Skype/SfbServer/help-topics/help-lscp/persistent-chat-category.md	✅Succeeded
Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration-main-page.md	✅Succeeded
Skype/SfbServer/help-topics/help-lscp/persistent-chat-configuration.md	✅Succeeded
Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy-main-page.md	✅Succeeded
Skype/SfbServer/help-topics/help-lscp/persistent-chat-policy.md	✅Succeeded
Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-backup-sql-server-store.md	✅Succeeded
Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-backup-sql-server-store.md	✅Succeeded
Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-compliance-sql-server-store.md	✅Succeeded
Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-file-store.md	✅Succeeded
Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-next-hop-page.md	✅Succeeded
Skype/SfbServer/help-topics/help-topobld/add-persistent-chat-sql-server-store.md	✅Succeeded
Skype/SfbServer/help-topics/help-topobld/call-admission-control-settings-expander.md	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/rooms/voice-and-face-recognition.md

• Line 145, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link '/powershell/module/teams/set-csteamsaipolicy?view=teams-ps"https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy?view=teams-ps"' will be broken in isolated environments. Replace with a relative link.

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions]

Too many files - PR blocked

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 108 files, which exceeds the block limit of 100. This PR will not be merged.

To merge this pull request

You must either reduce the number of files being changed to below the 100 file limit or split the changes into multiple PRs. PRs must not have more than 100 files and fewer than 30 files if possible.

To reject this pull request

If you want to abandon these changes and not merge this PR, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit 7fabe13:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/rooms/voice-and-face-recognition.md	💡Suggestion		Details
Teams/teams-administrative-units.md	💡Suggestion		Details
.openpublishing.redirection.json	✅Succeeded
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded
Teams/audio-conferencing-dial-out-usage-report.md	✅Succeeded
Teams/cloud-voice-network-settings.md	✅Succeeded
Teams/configure-lobby-sensitive-meetings.md	✅Succeeded
Teams/configure-meetings-baseline-protection.md	✅Succeeded
Teams/configure-meetings-highly-sensitive-protection.md	✅Succeeded
Teams/configure-meetings-three-tiers-protection.md	✅Succeeded
Teams/copilot-teams-transcription.md	✅Succeeded
Teams/cqd-intelligent-media-quality-classifiers.md	✅Succeeded
Teams/CQD-Power-BI-connector.md	✅Succeeded
Teams/customize-meeting-invitations.md	✅Succeeded
Teams/delete-exchange-online-transcripts.md	✅Succeeded
Teams/devices/authentication-best-practices-for-android-devices.md	✅Succeeded
Teams/devices/certified-device-apps.md	✅Succeeded
Teams/devices/certified-devices-overview.md	✅Succeeded
Teams/devices/certified-hardware-android.md	✅Succeeded
Teams/devices/common-area-mobile-phones.md	✅Succeeded	n/a (file deleted or renamed)
Teams/devices/media/edit-filter.png	✅Succeeded
Teams/devices/media/exclude-attribute-set.png	✅Succeeded
Teams/devices/media/include-all-apps-settings.png	✅Succeeded
Teams/devices/media/powershell-output-expected.png	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/rooms/voice-and-face-recognition.md

• Line 145, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link '/powershell/module/teams/set-csteamsaipolicy?view=teams-ps"https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy?view=teams-ps"' will be broken in isolated environments. Replace with a relative link.

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions]

Too many files - PR blocked

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 115 files, which exceeds the block limit of 100. This PR will not be merged.

To merge this pull request

You must either reduce the number of files being changed to below the 100 file limit or split the changes into multiple PRs. PRs must not have more than 100 files and fewer than 30 files if possible.

To reject this pull request

If you want to abandon these changes and not merge this PR, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit da47ae9:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/rooms/voice-and-face-recognition.md	💡Suggestion		Details
Teams/teams-administrative-units.md	💡Suggestion		Details
.openpublishing.redirection.json	✅Succeeded
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded
Teams/audio-conferencing-dial-out-usage-report.md	✅Succeeded
Teams/cloud-voice-network-settings.md	✅Succeeded
Teams/configure-lobby-sensitive-meetings.md	✅Succeeded
Teams/configure-meetings-baseline-protection.md	✅Succeeded
Teams/configure-meetings-highly-sensitive-protection.md	✅Succeeded
Teams/configure-meetings-three-tiers-protection.md	✅Succeeded
Teams/copilot-teams-transcription.md	✅Succeeded
Teams/cqd-intelligent-media-quality-classifiers.md	✅Succeeded
Teams/CQD-Power-BI-connector.md	✅Succeeded
Teams/customize-meeting-invitations.md	✅Succeeded
Teams/delete-exchange-online-transcripts.md	✅Succeeded
Teams/devices/authentication-best-practices-for-android-devices.md	✅Succeeded
Teams/devices/certified-device-apps.md	✅Succeeded
Teams/devices/certified-devices-overview.md	✅Succeeded
Teams/devices/certified-hardware-android.md	✅Succeeded
Teams/devices/collab-bar-deploy.md	✅Succeeded	n/a (file deleted or renamed)
Teams/devices/common-area-mobile-phones.md	✅Succeeded	n/a (file deleted or renamed)
Teams/devices/media/edit-filter.png	✅Succeeded
Teams/devices/media/exclude-attribute-set.png	✅Succeeded
Teams/devices/media/include-all-apps-settings.png	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/rooms/voice-and-face-recognition.md

• Line 145, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link '/powershell/module/teams/set-csteamsaipolicy?view=teams-ps"https://learn.microsoft.com/powershell/module/teams/set-csteamsaipolicy?view=teams-ps"' will be broken in isolated environments. Replace with a relative link.

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions]

Too many files - PR blocked

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 377 files, which exceeds the block limit of 100. This PR will not be merged.

To merge this pull request

You must either reduce the number of files being changed to below the 100 file limit or split the changes into multiple PRs. PRs must not have more than 100 files and fewer than 30 files if possible.

To reject this pull request

If you want to abandon these changes and not merge this PR, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit f4d1b74:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/app-ownership-developer-portal.md	💡Suggestion		Details
Teams/app-powered-tasks-in-planner.md	💡Suggestion		Details
Teams/direct-routing-whats-new.md	💡Suggestion		Details
Teams/shared-device-security-for-microsoft-teams.md	💡Suggestion		Details
Teams/sign-in-teams.md	💡Suggestion		Details
Teams/teams-administrative-units.md	💡Suggestion		Details
.github/workflows/BuildValidation.yml	✅Succeeded
.openpublishing.redirection.json	✅Succeeded
Skype/SfbOnline/audio-conferencing-in-office-365/phone-numbers-for-audio-conferencing.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/allow-users-to-contact-external-skype-for-business-users.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/configure-skype-for-business-settings-for-individual-users.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/let-skype-for-business-users-add-skype-contacts.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/set-up-skype-for-business-online.md	✅Succeeded
Skype/SfbOnline/skype-for-business-and-microsoft-teams-add-on-licensing/skype-for-business-and-microsoft-teams-add-on-licensing.md	✅Succeeded
Skype/SfbPartnerCertification/certification/archived/devices-usb-devices.md	✅Succeeded	n/a (file deleted or renamed)
Skype/SfbPartnerCertification/certification/archived/test-spec.md	✅Succeeded
Skype/SfbPartnerCertification/certification/devices-usb-devices.md	✅Succeeded
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/aa-cq-authorized-users-plan.md	✅Succeeded
Teams/aa-cq-authorized-users.md	✅Succeeded
Teams/aa-cq-cqd-historical-reports-v164.md	✅Succeeded
Teams/add-change-remove-emergency-location-organization.md	✅Succeeded
Teams/add-change-remove-emergency-place-organization.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded
Teams/alerts/teams-admin-alerts.md	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/app-ownership-developer-portal.md

• Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Teams/app-powered-tasks-in-planner.md

• Line 50, Column 47: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/businessscenario-planner-overview?view=graph-rest-beta
• Line 54, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenarioplanner-post-tasks?view=graph-rest-beta
• Line 55, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 56, Column 48: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 57, Column 61: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 58, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenarioplanner-delete-tasks?view=graph-rest-beta
• Line 113, Column 58: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/plannerexternalreferences?view=graph-rest-beta
• Line 234, Column 3: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/businessscenario-planner-overview?view=graph-rest-beta

Teams/direct-routing-whats-new.md

• Line 73, Column 54: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /microsoft-365/compliance/encryption-office-365-tls-certificates-changes?view=o365-worldwide

Teams/shared-device-security-for-microsoft-teams.md

• Line 62, Column 288: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /microsoft-365/security/office-365-security/overview?view=o365-worldwide

Teams/sign-in-teams.md

• Line 183, Column 60: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/intune-apps-manageddevicemobileappconfiguration?view=graph-rest-1.0

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions]

Too many files - PR blocked

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 379 files, which exceeds the block limit of 100. This PR will not be merged.

To merge this pull request

You must either reduce the number of files being changed to below the 100 file limit or split the changes into multiple PRs. PRs must not have more than 100 files and fewer than 30 files if possible.

To reject this pull request

If you want to abandon these changes and not merge this PR, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit 71c332d:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/app-ownership-developer-portal.md	💡Suggestion		Details
Teams/app-powered-tasks-in-planner.md	💡Suggestion		Details
Teams/direct-routing-whats-new.md	💡Suggestion		Details
Teams/shared-device-security-for-microsoft-teams.md	💡Suggestion		Details
Teams/sign-in-teams.md	💡Suggestion		Details
Teams/teams-administrative-units.md	💡Suggestion		Details
.github/workflows/BuildValidation.yml	✅Succeeded
.openpublishing.redirection.json	✅Succeeded
Skype/SfbOnline/audio-conferencing-in-office-365/phone-numbers-for-audio-conferencing.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/allow-users-to-contact-external-skype-for-business-users.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/configure-skype-for-business-settings-for-individual-users.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/let-skype-for-business-users-add-skype-contacts.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/set-up-skype-for-business-online.md	✅Succeeded
Skype/SfbOnline/skype-for-business-and-microsoft-teams-add-on-licensing/skype-for-business-and-microsoft-teams-add-on-licensing.md	✅Succeeded
Skype/SfbPartnerCertification/certification/archived/devices-usb-devices.md	✅Succeeded	n/a (file deleted or renamed)
Skype/SfbPartnerCertification/certification/archived/test-spec.md	✅Succeeded
Skype/SfbPartnerCertification/certification/devices-usb-devices.md	✅Succeeded
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/aa-cq-authorized-users-plan.md	✅Succeeded
Teams/aa-cq-authorized-users.md	✅Succeeded
Teams/aa-cq-cqd-historical-reports-v164.md	✅Succeeded
Teams/aa-cq-cqd-historical-reports.md	✅Succeeded
Teams/add-change-remove-emergency-location-organization.md	✅Succeeded
Teams/add-change-remove-emergency-place-organization.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/app-ownership-developer-portal.md

• Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Teams/app-powered-tasks-in-planner.md

• Line 50, Column 47: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/businessscenario-planner-overview?view=graph-rest-beta
• Line 54, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenarioplanner-post-tasks?view=graph-rest-beta
• Line 55, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 56, Column 48: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 57, Column 61: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 58, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenarioplanner-delete-tasks?view=graph-rest-beta
• Line 113, Column 58: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/plannerexternalreferences?view=graph-rest-beta
• Line 234, Column 3: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/businessscenario-planner-overview?view=graph-rest-beta

Teams/direct-routing-whats-new.md

• Line 73, Column 54: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /microsoft-365/compliance/encryption-office-365-tls-certificates-changes?view=o365-worldwide

Teams/shared-device-security-for-microsoft-teams.md

• Line 62, Column 288: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /microsoft-365/security/office-365-security/overview?view=o365-worldwide

Teams/sign-in-teams.md

• Line 183, Column 60: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/intune-apps-manageddevicemobileappconfiguration?view=graph-rest-1.0

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions]

Too many files - PR blocked

This public repo applies limits on the number of files that can be merged in a single pull request (PR):

• Warning Warning message and ability to unblock PR using the Merge large pull request^* label - 30
• Block Block message and PR is blocked - 100

This pull request will change 378 files, which exceeds the block limit of 100. This PR will not be merged.

To merge this pull request

You must either reduce the number of files being changed to below the 100 file limit or split the changes into multiple PRs. PRs must not have more than 100 files and fewer than 30 files if possible.

To reject this pull request

If you want to abandon these changes and not merge this PR, click Close pull request at the bottom of this page to close it without merging. Work with your team to revert any changes that aren't correct.

^* You must have write or triage access to this repo to add labels.

[learn-build-service-prod]

Learn Build status updates of commit 96ba286:

💡 Validation status: suggestions

File	Status	Preview URL	Details
Teams/app-ownership-developer-portal.md	💡Suggestion		Details
Teams/app-powered-tasks-in-planner.md	💡Suggestion		Details
Teams/direct-routing-whats-new.md	💡Suggestion		Details
Teams/shared-device-security-for-microsoft-teams.md	💡Suggestion		Details
Teams/sign-in-teams.md	💡Suggestion		Details
Teams/teams-administrative-units.md	💡Suggestion		Details
.github/workflows/BuildValidation.yml	✅Succeeded
.openpublishing.redirection.json	✅Succeeded
Skype/SfbOnline/audio-conferencing-in-office-365/phone-numbers-for-audio-conferencing.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/allow-users-to-contact-external-skype-for-business-users.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/configure-skype-for-business-settings-for-individual-users.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/let-skype-for-business-users-add-skype-contacts.md	✅Succeeded
Skype/SfbOnline/set-up-skype-for-business-online/set-up-skype-for-business-online.md	✅Succeeded
Skype/SfbOnline/skype-for-business-and-microsoft-teams-add-on-licensing/skype-for-business-and-microsoft-teams-add-on-licensing.md	✅Succeeded
Skype/SfbPartnerCertification/certification/archived/devices-usb-devices.md	✅Succeeded	n/a (file deleted or renamed)
Skype/SfbPartnerCertification/certification/archived/test-spec.md	✅Succeeded
Skype/SfbPartnerCertification/certification/devices-usb-devices.md	✅Succeeded
Skype/SfBServer2019/virtualization-guidance.md	✅Succeeded
Teams/aa-cq-authorized-users-plan.md	✅Succeeded
Teams/aa-cq-authorized-users.md	✅Succeeded
Teams/aa-cq-cqd-historical-reports-v164.md	✅Succeeded
Teams/aa-cq-cqd-historical-reports.md	✅Succeeded
Teams/add-change-remove-emergency-location-organization.md	✅Succeeded
Teams/add-change-remove-emergency-place-organization.md	✅Succeeded
Teams/advanced-collaboration-analytics.md	✅Succeeded

This comment lists only the first 25 files in the pull request.

Teams/app-ownership-developer-portal.md

• Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Teams/app-powered-tasks-in-planner.md

• Line 50, Column 47: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/businessscenario-planner-overview?view=graph-rest-beta
• Line 54, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenarioplanner-post-tasks?view=graph-rest-beta
• Line 55, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 56, Column 48: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 57, Column 61: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenariotask-update?view=graph-rest-beta
• Line 58, Column 26: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/businessscenarioplanner-delete-tasks?view=graph-rest-beta
• Line 113, Column 58: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/plannerexternalreferences?view=graph-rest-beta
• Line 234, Column 3: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/businessscenario-planner-overview?view=graph-rest-beta

Teams/direct-routing-whats-new.md

• Line 73, Column 54: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /microsoft-365/compliance/encryption-office-365-tls-certificates-changes?view=o365-worldwide

Teams/shared-device-security-for-microsoft-teams.md

• Line 62, Column 288: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /microsoft-365/security/office-365-security/overview?view=o365-worldwide

Teams/sign-in-teams.md

• Line 183, Column 60: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/resources/intune-apps-manageddevicemobileappconfiguration?view=graph-rest-1.0

Teams/teams-administrative-units.md

• Line 43, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 44, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 45, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 46, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-scope
• Line 47, Column 119: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: /graph/api/rbacapplication-post-roleassignments?view=graph-rest-1.0&tabs=powershell#example-2--create-a-role-assignment-with-administrative-unit-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.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel