New post: Taming Pay-As-You-Go Billing in Power Platform#293
Open
rranjit83 wants to merge 5 commits into
Open
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Removed duplicate H1 title (Chirpy renders front matter title as H1) - Updated tags from 3 generic to 8 specific tags for better Further Reading overlap Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a new Copilot Studio CAT blog post on governing Power Platform Pay-As-You-Go (PAYG) spend at scale, plus supporting author metadata and a small tooling-permissions change.
Changes:
- Adds a new post describing bulk billing-policy assignment (PowerShell) and automated unlinking based on Azure Budget thresholds.
- Adds two new author entries in
_data/authors.yml. - Expands
.claude/settings.local.jsontool permissions to allowcurl.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
.claude/settings.local.json |
Broadens allowed Bash commands (adds curl). |
_posts/2026-05-05-managing-spend-pay-as-you-go.md |
New long-form post covering PAYG billing policy management and spend guardrails. |
_data/authors.yml |
Adds author profiles for the new post. |
Comment on lines
+4
to
+5
| "Bash(git checkout:*)", | ||
| "Bash(curl *)" |
| categories: [copilot-studio, licensing] | ||
| tags: [pay-as-you-go, billing-policy, power-automate, governance, azure-automation, power-platform, licensing, powershell] | ||
| description: "How do you manage Azure consumption when using Pay as you go with Copilot Studio?" | ||
| author: [rranjit,zekitekin] |
Comment on lines
+20
to
+33
| So. You've embraced Pay-As-You-Go (PAYG) for Power Platform and Copilot Studio. Congratulations — you're now enjoying the beautiful freedom of consumption-based billing, where every maker in your organization can spin up AI-powered flows and agents without needing a license purchase order approved by three committees and a notary. | ||
|
|
||
| And then the bill arrived. | ||
|
|
||
| Not a *catastrophic* bill, necessarily. But enough to make you sit up straight, squint at your Azure Cost Management dashboard, and mutter something unprintable.... | ||
|
|
||
| This is the blog post for you. | ||
|
|
||
| We're going to walk through two very practical things: | ||
|
|
||
| 1. **Bulk-assigning environments to billing policies by name** — because pointing-and-clicking through the Power Platform Admin Center for 47 environments is not a career strategy. | ||
| 2. **Automatically unlinking environments from billing policies when your budget threshold is breached** — because automated guardrails are more reliable than hoping someone notices the alert email before the weekend. | ||
|
|
||
| Let's go. |
|
|
||
| ## A Quick Refresher: What Are Billing Policies? | ||
|
|
||
| Think of a billing policy as the financial passport for your Power Platform environments. It links an environment to an Azure subscription, which is how PAYG consumption — Copilot Studio message packs, AI Builder credits, and the like — gets charged back. Without a billing policy linked, an environment falls back on seeded capacity or simply can't access the premium features. |
| ```powershell | ||
| $aud = "https://service.flow.microsoft.com/" | ||
| $EntraToken = Get-AzAccessToken -ResourceUrl $aud | ||
| $Token = $EntraToken.Token | ConvertTo-SecureString -AsPlainText |
Comment on lines
+316
to
+322
| Trigger the runbook manually against it: | ||
|
|
||
| ```powershell | ||
| az automation runbook start ` | ||
| --name UnlinkBillingPolicies ` | ||
| --resource-group Azurevnetforpowerplatform ` | ||
| --automation-account-name RRANJITBillingPolicy ` |
| zekitekin: | ||
| name: Zeki Tekin | ||
| email: zekitekin@microsoft.com | ||
| avatar: https://github.com/rranjit.png |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Checklist
/review-postand addressed feedback./tools/run.sh)