Skip to content

Update manage-billing-across-tenants.md#128506

Open
FriKuma wants to merge 1 commit into
MicrosoftDocs:mainfrom
FriKuma:patch-1
Open

Update manage-billing-across-tenants.md#128506
FriKuma wants to merge 1 commit into
MicrosoftDocs:mainfrom
FriKuma:patch-1

Conversation

@FriKuma
Copy link
Copy Markdown

@FriKuma FriKuma commented May 18, 2026

Hi Justin,
Per our chat, I am adding screenshots depicting the subscription flow for MCA customer feedback. I have shared the document comprising changes with you as well. Please review and let me know if you have any questions.

Link: Manage billing across multiple tenants - Microsoft Cost Management | Microsoft Learn

Thanks,
Jyoti

@prmerger-automator
Copy link
Copy Markdown
Contributor

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

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 177cf46:

✅ Validation status: passed

File Status Preview URL Details
articles/cost-management-billing/manage/manage-billing-across-tenants.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner
Copy link
Copy Markdown
Contributor

v-regandowner commented May 18, 2026

@FriKuma - Please note that it looks like you didn't actually add the images, just placeholder text. Review this content for instructions and consider closing this PR and opening a new one in the private repository: azure-docs-pr


@jkinma39

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

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged tracking label for the PR review team label May 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants