Add clarification for SMTP username parameter

[ahmadfoa]

Clarified the SMTP username format in the PowerShell instructions to reduce customer confusion.

[prmerger-automator]

@ahmadfoa : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 4faf27c:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-powershell.md	⚠️Warning		Details

articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-powershell.md

• Line 32, Column 31: [Warning: disallowed-html-tag - See documentation] HTML tag 'SMTP' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
• Line 33, Column 47: [Warning: disallowed-html-tag - See documentation] HTML tag 'Azure' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
• Line 33, Column 92: [Warning: disallowed-html-tag - See documentation] HTML tag 'Microsoft' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
• Line 33, Column 125: [Warning: disallowed-html-tag - See documentation] HTML tag 'Microsoft' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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.

[ttorble]

@ddouglas-msft

Can you review the proposed changes? Note that before the PR can be merged you'll need to remove the explanation for the proposed update from the article and resolve the warnings in the PR by marking the user name as code. Thanks

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[Copilot]

Pull Request Overview

This PR clarifies the SMTP username parameter format in PowerShell documentation to help customers better understand the expected format.

Key Change:

• Added documentation explaining the SMTP username format structure

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The documentation contains informal phrasing that should be rewritten in a more professional style. Remove the meta-commentary ('it is causing confusion for customers, so it would be better to add this clarification') and rephrase as direct instructional content. Additionally, 'your username-' appears to have incorrect punctuation and unclear meaning.

Suggested change

	Regarding the -ArgumentList '<SMTP Username>' parameter, it is causing confusion for customers, so it would be better to add this clarification
	- The SMTP username should be your username- <Azure Communication Services Resource name>.<Microsoft Entra Application ID>.<Microsoft Entra Tenant ID>
	The -ArgumentList '<SMTP Username>' parameter requires the SMTP username in the following format:
	- <Azure Communication Services Resource name>.<Microsoft Entra Application ID>.<Microsoft Entra Tenant ID>

[Copilot]

There should be a space after the hyphen in 'username-'. The correct format should be 'username - ' or the hyphen should be removed entirely depending on the intended meaning.

Suggested change

	- The SMTP username should be your username- <Azure Communication Services Resource name>.<Microsoft Entra Application ID>.<Microsoft Entra Tenant ID>
	- The SMTP username should be your username - <Azure Communication Services Resource name>.<Microsoft Entra Application ID>.<Microsoft Entra Tenant ID>