Work IQ lets Copilot write back to your source records
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 / Product coverage
Dataverse
Source-linked reporting organized by product, platform, and the topics that connect them.
Latest coverage
Microsoft pays double for cross-tenant Power Platform bugs
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.
Power Platform CLI now reaches the whole tenant
Microsoft put more than 200 auto-generated API commands into the Power Platform CLI preview. Governance and licensing are now a script away.
PPCC 2026 agent demos need a process owner in the room
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.
Match each Dynamics 365 planning decision to a roadmap channel
Microsoft's AI at Work roadmap, Message Center, and Learn each answer a different planning question. Here is which channel each decision belongs to.
PPCC 2026's procurement example gets the approval step right
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.
PPCC 2026's procurement agent needs one record it writes to
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.
One Microsoft roadmap still needs a release owner in your tenant
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.
AI at Work roadmap and Message Center answer different questions
Microsoft's August 25 post keeps public roadmap items and tenant change notices in separate channels. Someone on your team has to join them.
Getting your team ready for the AI at Work roadmap switch
Microsoft retires Release Planner on November 15, 2026. What admins and architects should export, rebookmark, and reschedule before that date.
Analysis and architecture
Cloud flow or plugin for Dataverse business logic
A plugin can stop a bad save and a cloud flow cannot. That difference, plus who maintains it, settles most calls.
Dataverse security that survives ten times the size
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.
Movers break the identity lifecycle across business apps
Provisioning is the easy part. Transfers add access and almost never remove it, and every application keeps entitlement in a model of its own.
The Power Platform setting most admins have never set
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.
When Dataverse reporting needs more than Power BI
Most reporting on Dynamics 365 and Dataverse data never needed a data platform. Copying it out earns the cost only when history, joins or scan volume demand it.
Power Pages identity decisions that are hard to undo
A Power Pages site authenticates against an identity provider and authorises against a Dataverse contact. Matching the two on email is the mistake that lasts.
Dataverse or SharePoint lists, and how to decide
SharePoint lists are the right store more often than architects admit. Delegation limits are where they quietly stop being right, and nothing errors when they do.
Service accounts are the least governed identity you run
Integration accounts miss every joiner and leaver process. Give each one a named owner, a readable name, narrow scopes and a rehearsed rotation.
Extend Account or build a custom Dataverse table
A decision framework for the Dataverse call every team faces, when a requirement belongs as columns on Account and when it needs its own table.
Give every Dataverse access exception an owner and an expiry
Access exceptions in Dataverse and ServiceNow outlive their reason. Give each one a named owner, an end date, and a record small enough to review.
Cut every Power BI tile that cannot name a decision
A Power BI tile earns its place by naming the decision it changes, the value that triggers it, and the person who acts. Everything else is a report.
Who gets to define revenue in Power BI and Data Cloud
Sales, finance, and operations each hold a correct definition of revenue. A semantic model picks one and hides the rest, so name a steward before it does.
Related guides
Power Apps delegation and the total that comes back wrong
A query your data source cannot evaluate still returns an answer, built from part of the table, and sample data will never show you the gap.
Why your Power Pages site is slow for everyone else
A portal is fast on an administrator's laptop and slow on a customer's phone. Fix permission scope, list design and image weight before launch.
Power BI row-level security for Dataverse data
A Power BI import carries everything the refresh account could read. Rebuild the row filters, maintain the mapping table, and test as a restricted user.
What to check before a Power Pages site goes public
A table permission granted for one page applies everywhere that table can be reached. Check the whole surface before a Power Pages site faces the internet.
What is actually eating your Dataverse capacity
Most Dataverse growth comes from attachments, audit rows, trace logs and environments nobody deleted. The per-table view in the admin center names yours.
What Dataverse actually is, and when it is overkill
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.
When to hire a Dataverse consultant and what to ask
Plenty of Dataverse walls are a training or licensing problem. Pay for outside help when the model, the security map, or the scale is beyond your team.
How many Power Platform environments you actually need
A working rule for deciding which Power Platform solutions get their own dev, test, and production environments, and who approves promotion between them.
Build a Power Platform ALM pipeline makers actually use
A pipeline survives when the build takes under two minutes, test data looks real, and a maker can roll back without opening a ticket.
Governance that keeps Power Platform makers building
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.
Write the analytics questions before the Dataverse schema
Power BI can only answer what the Dataverse model was built to hold. Write the leader's questions first, with the decision, grain, and freshness each needs.
Business keys that survive a Dataverse or Sales Cloud rebuild
Match on the number the business already reads out, enforce it as a unique field on both sides, and test the missing, repeated, and near-twin key first.
A release checklist for shared Power Platform solutions
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.