
Self-service Power Pages ownership transfer has no undo
Power Pages site owners can now be reassigned without a support case, and Microsoft's own documentation says the transfer cannot be automatically undone.
Microsoft / Product coverage
Source-linked reporting organized by product, platform, and the topics that connect them.

Power Pages site owners can now be reassigned without a support case, and Microsoft's own documentation says the transfer cannot be automatically undone.

Microsoft now hosts Copilot-generated code inside the tenant boundary, and the admin center inventory matters more than the hosting does.

Work IQ public preview opens September 30 with governed actions that write changes back to source records inside the permissions your users already hold.

Microsoft's Field Service scheduling agent is moving to recurring runs that write optimised bookings onto the board with no dispatcher starting them.

Microsoft's updated Power Platform bounty schedule pays double for critical cross-tenant flaws and names Dataverse twice. Here is what an admin should check.

Microsoft now provisions and renews SSL and TLS certificates for Power Pages custom domains, but the option does not appear when CDN or WAF is enabled.

Microsoft says Server Logic in Power Pages can now invoke Power Automate cloud flows, which puts an externally facing form in front of 1,400 connectors.

Microsoft's app-builder skill reached GA covering security roles and business rules. What that changes for Power Platform review, ALM and connectors.

Microsoft put more than 200 auto-generated API commands into the Power Platform CLI preview. Governance and licensing are now a script away.

Dynamics 365 Activate profiles a company's whole Salesforce data set before migration starts, already at billions of records. That access needs scrutiny.

Microsoft's PPCC 2026 preview asks attendees to bring one process. The stage agent will work either way. What decides the pilot is who owns that process.

Microsoft's AI at Work roadmap, Message Center, and Learn each answer a different planning question. Here is which channel each decision belongs to.

Microsoft's PPCC 2026 procurement example sends only higher-risk exceptions to a person. Most approval steps in a live tenant would fail that test.

Microsoft's PPCC 2026 preview runs a procurement request through Copilot, an agent, a workflow, and a reviewer. We'd ask which Dataverse row holds the trace.

Microsoft's always-on AI at Work roadmap removes the wave date that used to force a review. Someone in your tenant now has to own that date.

Microsoft's August 25 post keeps public roadmap items and tenant change notices in separate channels. Someone on your team has to join them.

Microsoft retires Release Planner on November 15, 2026. What admins and architects should export, rebookmark, and reschedule before that date.

An integration belongs to neither system team, so it goes unowned. What the owner role really involves, and why it is a stronger career position than it looks.

Business units, depth, teams and sharing decide whether a Dataverse security model survives growth. How to design each one so it still makes sense later.

Agents can build the field, the flow and the report. What they cannot do is know why your configuration looks the way it does, or which request to refuse.

Consumption pricing moves the spending decision into engineering. Attribute usage to owning teams and capture a baseline before the rate changes.

Release waves are gone, so the release channel on each environment now decides when your users meet change. Most estates have never deliberately set it.

Winter '27 lands October 12, the Release Planner retires November 15, Brazil is arriving and 2026R2 is already live. Six vendors, one team calendar.

Agents are absorbing the configuration work, and the premium is moving to judgement, boundaries and saying no.

Microsoft is retiring the twice-yearly release wave model. Release plans stop publishing in September 2026 and the Release Planner retires by November 15.

The two products share most of their design. The real choice is who owns the thing in two years, which budget pays, and who gets paged at 2am.

ServiceNow captures changes as you make them and Power Platform packages what already exists. Standardise the rules around both instead of merging them.

The same validation in the form, the flow and the ERP is a tradeoff nobody wrote down. Pick the layer by who must never be able to break the rule.

A certification is worth the week when a partner badge, a procurement filter or a thin CV depends on it. For a proven in-house admin, rarely.

Power Automate flows belong to whoever built them, and that single fact quietly creates most of the ownership debt in a mature Power Platform tenant.

A concrete method for sorting Power Platform's twice-yearly release waves and daily message center posts from noise into action.

A connector gets a record from one system to another. An integration owns what happens when the record gets rejected, and most sync projects fail without that part.

An unused seat still gets billed. Cross usage logs against the assignment list, flag the quiet accounts, and reclaim seats before renewal locks the price in.

Fifty people can end up depending on a canvas app with no source control and one maker who understands it, long before anyone decides that on purpose.

Before a Power Platform or SAP roadmap gets sequenced, list every flow it touches with a source of record, a consumer, and the person who fixes exceptions.

A catalog entry for a Power Platform flow should name who gets paged, what to check first, and who can switch it off. The design document stays where it is.

A flow that stops is visible in run history. A flow that half-finishes leaves two systems disagreeing, so design the handlers, retries and owner first.

The scripts and business rules inside your instance outlive whoever wrote them. Record why the logic exists, keep it in one place, and fail loudly.

Most Dataverse growth comes from attachments, audit rows, trace logs and environments nobody deleted. The per-table view in the admin center names yours.

Dataverse gives you a relational model, row and column security, and rules that hold whoever wrote the record. A five person spreadsheet needs none of it.

A working rule for deciding which Power Platform solutions get their own dev, test, and production environments, and who approves promotion between them.

A pipeline survives when the build takes under two minutes, test data looks real, and a maker can roll back without opening a ticket.

A fifteen-minute conversation before the first screen is built, recorded on the Dataverse solution, does more than an approval form completed after go-live.

The four numbers a platform owner needs before a Power Platform, Dynamics 365, or Agentforce repackaging note gets forwarded to finance.

The questions a platform team should ask before a shared Power Platform solution reaches other makers, and where to keep the answers for the next owner.

A center of excellence earns its keep with office hours and a pattern library, and loses it the day it starts approving every app or owning every maker's flow.