@byszhoubin, the monikers in the topics are correct. Per work items https://ceapex.visualstudio.com/Engineering/_workitems/edit/231986 and https://ceapex.visualstudio.com/Engineering/_workitems/edit/224630 the moniker values in the topics are correct. Therefore, instead of removing the monikers from all topics, I updated the docfx.json to match the moniker values in the topics.

Closing this PR.

@chrisda Thanks for the update, we'll take a try of the new config with docfx-v3.

@chrisda The PowerShell reference build pipeline doesn't support monikerRange, which is designed for other types of documentation. Can we clean up the monikerRange from the YAML header, which is blocking docfx v3 rollout?

Docs Build status updates of commit 2c06687:

🕙 Full build: the average full build time is 17 min(s) 31 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 2c06687:

⚠️ Validation status: warnings

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

exchange/exchange-ps/exchange/Set-MalwareFilteringServer.md

• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings 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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

Docs Build status updates of commit 6b8e427:

🕙 Full build: the average full build time is 17 min(s) 37 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 6b8e427:

⚠️ Validation status: warnings

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

exchange/exchange-ps/exchange/Set-MalwareFilteringServer.md

• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
• Line 198: [Warning-insecure-link] Link 'http://forefrontdl.microsoft.com/server/scanengineupdate' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings 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 in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

Docs Build status updates of commit 0c9084b:

🕙 Full build: the average full build time is 17 min(s) 37 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 0c9084b:

✅ Validation status: passed

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel