Default scope of reservation transfer to a tenant

[RajeevMSFT]

This update covers the default scope of the reserved instance after it is transferred to the new Tenant and if we do not specify the new scope of reserved instance.

[prmerger-automator[bot]]

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

[learn-build-service-prod[bot]]

Learn Build status updates of commit 21e262d:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/cost-management-billing/reservations/troubleshoot-reservation-transfers-between-tenants.md	:white_check_mark:Succeeded

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

[Court72]

@bandersmsft

Can you review the proposed changes?

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

[bandersmsft]

sign-off

[learn-build-service-prod[bot]]

Learn Build status updates of commit 5c83acd:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/cost-management-billing/reservations/troubleshoot-reservation-transfers-between-tenants.md	:white_check_mark:Succeeded

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