Publish: Real-Time PAYG Overage Protection (review + fixes)

[adilei]

Reviews and publishes rranjit's PAYG overage protection post, which was previously merged via #295 but left as published: false.

What changed

Publishing

• published: false -> true
• Re-dated 2026-05-07 -> 2026-06-12 (file renamed) so it appears at the top of the blog and, importantly, sits after its prerequisite post instead of before it.

Build / render fixes

• Fixed a broken post_url (2026-05-05 -> 2026-05-13-managing-spend-pay-as-you-go). This would have broken the Jekyll build on publish, since the wrong slug only went unnoticed while the post was unpublished.
• Converted a broken >Note: blockquote into a Chirpy .prompt-info callout.
• Converted the end-to-end ASCII diagram to a Mermaid flowchart (mermaid: true), matching the sibling post.

Content / consistency

• Resolved the 4-hour vs hourly contradiction: the Core Idea argues 4 hours is the correct cadence (Azure refreshes cost data every 4h), but the trigger example, scenario, and pros/cons promoted hourly / 15-min polling. Aligned all of them to 4 hours.
• Added a second contextual internal link to the prerequisite post.
• Fixed typos: Coustom, POlicy, occassionally, Thats, power platform -> Power Platform; cleaned up the title's trailing comma.
• Trimmed em-dash usage in prose per the style guide.

Verified with bundle exec jekyll build (clean) and previewed locally.

[github-actions]

Blog preview check passed for 3c7e16e.

The Jekyll site compiled successfully. No newly added _posts/*.md files were detected in this PR.

[adilei]

@rranjit83 one content request for the Authentication section of Component 1 (the Cost Management custom connector):

Readers consistently get stuck on the OAuth 2.0 setup. The text lists the Authorization URL, Token URL, Resource/Audience, and Client ID/Secret, but the OAuth configuration screen in the custom connector editor trips people up.

Could you add a screenshot of the custom connector's Security tab showing the OAuth 2.0 / Azure AD configuration filled in (Authorization URL, Token URL, Resource URL = https://management.azure.com/, and where the Client ID/Secret go)? That single screenshot would unblock most people.

Please drop the image in assets/posts/managing-azure-consumption-power-platform/ with alt text + an italic caption, placed right after the bullet list in the Authentication section.

[adilei]

@rranjit83 this is ready for your review. Summary of what I changed while preparing it for publication:

Publishing

• Flipped published: false → true and re-dated the post to 2026-06-12 (file renamed) so it lands at the top of the blog and, importantly, after its prerequisite post instead of before it.

Build / correctness

• Fixed a broken post_url (2026-05-05 → 2026-05-13-managing-spend-pay-as-you-go) that would have failed the build on publish.
• Deep-linked the Subscription ID / Resource Group prerequisite to the 'What Are Billing Policies?' section of the previous post.
• Repointed all solution/connector download links from rranjit83/AgentDemoSamples to the official microsoft/CopilotStudioSamples (infrastructure/manage-paygo).

Structure (why → how → deep dive)

• Renamed 'Architecture Overview' → 'What the Solution Contains'.
• Added a 'Get It Running (The Short Path)' quick-start section (import, configure connections, set variables, confirm the 4-hour recurrence, turn on) right after Prerequisites.
• Moved 'The Core Idea' below the quick start so it leads the how-it-works deep dive.
• Put the literal OAuth connection values in the configuration step (where you need them); Component 1's Authentication now explains the mechanism and links back.

Content / polish

• Resolved the 4-hour vs hourly contradiction across the trigger, scenario, and pros/cons.
• Converted the bare >Note: blockquotes to Chirpy prompt boxes and the ASCII end-to-end diagram to Mermaid.
• Fixed typos (Coustom, POlicy, occassionally, Thats, etc.), cleaned the title, trimmed em-dashes, and rewrote the header image alt as a whimsical caption.

One open request: please add a screenshot of the custom connector's OAuth 2.0 / Azure AD Security tab in the Authentication section (see my earlier comment) — readers consistently get stuck there.

Let me know if anything misrepresents the solution's behaviour.