Docs Build status updates of commit b8dd342:

✅ Validation status: passed

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 the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit 9f6e826:

✅ Validation status: passed

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 the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Copy review - @JensTrier, kindly commit the suggested changes. Many thanks.

Thanks & Done!

Docs Build status updates of commit 7e91af4:

✅ Validation status: passed

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 the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

@dariomws @tseward @get-itips

@yogkumgit I would like to add the following info to the Outputs section with two examples. Can I do it in this PR or should I create a new one?

On successful execution of the command no result object is present. On failed execution of the command, a result object is present with a Code string parameter to indicate the error code and a Message string parameter with the additional error or warning message.

Hi @JensTrier, you can do it in this PR while it's still open.

Docs Build status updates of commit 8fd085b:

✅ Validation status: passed

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 the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

I've now added text to description section in both cmdlet files and added a new example to Set-CsPhoneNumberAssignment show the result object. Please have a look

Docs Build status updates of commit 989b1ea:

✅ Validation status: passed

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 the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

@JohanFreelancer9 @tseward @get-itips, please review the latest addition.

@tiburd Please merge this PR. Thanks

Docs Build status updates of commit 3235c19:

✅ Validation status: passed

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 the docs.microsoft.com contributor guides
• Post your question in the Docs support channel