If you blinked this week, you missed some major Power Platform announcements. From security lockdowns to tool retirements and powerful new admin capabilities, February 2026 is shaping up to be a month of real change.
Here’s what actually matters—no fluff, just the updates you need to know about.
Let's explore
🔒 Security First: Tenant Isolation Goes Live February 1st
MC1221422 – This one demands your attention. Starting February 1, 2026, tenant isolation becomes the default for all Power Platform tenants. Translation? Cross-tenant connections get blocked—inbound, outbound, or both—unless you explicitly allow them.
If your workflows depend on cross-tenant connections, configure your tenant isolation policy before February 1st. Do nothing, and those connections stop working. Guest user access stays untouched, but connector traffic between tenants? That’s getting locked down tight.
Action needed: Review your cross-tenant dependencies now. Set up allowlists or disable tenant isolation entirely if needed—but decide before the enforcement date.
📊 Power BI News: Say Goodbye to Q&A (and That Old SharePoint Webpart)
Q&A Is Officially Retiring
MC1218421 – Power BI Q&A, the legacy natural language query tool, retires in December 2026. Microsoft is pushing everyone toward Power BI Copilot instead—a more advanced AI-powered solution that eliminates feature overlap.
After December 2026, existing Q&A visuals stop working. No new Q&A visuals can be created. Q&A Setup tools (synonyms, linguistic relationships) also disappear.
What to do: Audit your reports and dashboards. Identify Q&A visuals and start migrating to Copilot experiences. Update your internal docs and helpdesk scripts while you’re at it.
SSRS SharePoint Webpart Support Ends April 13th
MC1217651 – The SQL Server Reporting Services (SSRS) Report Viewer SharePoint Webpart loses support on April 13, 2026. It’ll still work, but Microsoft won’t maintain it.
The fix: Embed SSRS reports in SharePoint using URL parameters instead. Check the URL Access Parameter Reference documentation for the step-by-step.
Copilot Capacity Designation: Now On By Default
MC1217152 (High relevance) – Starting February 12, 2026, the tenant setting “Capacities can be designated as Fabric Copilot capacities” turns on by default for all tenants.
This doesn’t change existing capacity configs—it just enables the setting. If you haven’t enabled capacities for Fabric Copilot yet, nothing changes for you. But capacity admins will see the toggle flipped on.
Want to opt out? Turn the setting on, then immediately turn it off before rollout. That signals you’ll enable Copilot capacities later, and Microsoft skips the auto-update.
🛠️ Power Platform Admin Center Gets Serious Upgrades
Power Platform Inventory Is Now Generally Available
MC1223778 – The Power Platform inventory feature just hit GA. You can now view and manage agents, apps, flows, environments, and environment groups—all in one place.
Access it from the unified Inventory page under Manage, or check resource-specific views in Copilot Studio, Power Apps, and Power Automate. On February 9, 2026, environment group support and the Power Platform for Admins V2 connector arrive, plus the “Preview” tag disappears completely.
Pull inventory data via the Power Platform for Admins V2 connector, Power Platform Inventory API, or Azure Resource Graph.
New Usage Experience Rolling Out
MC1220728 – The new usage experience in PPAC started rolling out January 20, 2026, with full availability by February 2, 2026. Admins get powerful insights into adoption trends, top-used resources, and platform engagement.
This is pure visibility—track what’s driving engagement, spot trends, and make data-driven decisions.
Copilot Adoption Tracking Gets Better
MC1218332 – The Copilot Studio page in PPAC now shows expanded insights when you select an agent. Expect usage data over the last 30 days, activity success rates with visual breakdowns, and interactive charts showing monthly trends. This went GA on January 16, 2026.
Environments Page Cleanup
MC1226444 – As of February 3, 2026, the Manage option and release wave label disappear from the Updates card on the Environments page. A new link titled “Release Wave opt-in has moved!” takes their place. Environment behavior now depends on Release Channel settings.
⚡ Power Automate: Debugging and Desktop Flow Enhancements
Environment Variables in Desktop Flows
MC1226018 – Starting February 28, 2026, retrieve Power Platform Environment variables directly in desktop flows. No more passing them as inputs—just grab them straight from the environment.
Inline Property View in Cloud Flow Designer
MC1218891 – On February 10, 2026, the new cloud flow designer lets you view property values expanded inline. Check property values from multiple steps at once when authoring or debugging flows.
Debug Condition Actions at Runtime
MC1218294 – This one already went GA on December 31, 2025. View detailed results for each row in a condition action, including values in dynamic content and expressions. If you’re wrestling with complex condition logic, this just got way easier.
🤖 Copilot Studio: Smarter Agents, Better Controls
Dynamic Filtering for Knowledge Sources
MC1223795 – Filter which knowledge sources your agents can access. Goes GA February 28, 2026. Streamline workflows and optimize response relevance by controlling what agents tap into.
Draft with Copilot
MC1165633 – Available February 28, 2026, this feature helps you write or rewrite prompts using Copilot. Turn your intent into a more effective prompt that follows best practices. Copilot can also generate sample test data for quicker validations.
Content Moderation Settings
MC1217615 – Launching January 31, 2026, adjust content moderation levels for AI prompts in Copilot Studio and Power Platform. Lower moderation = higher risk of harmful content but more responses. Higher moderation = lower risk but fewer responses. You control the balance via the settings panel in the prompt builder.
Bing Query Data Terms Update
MC1225193 – Early February 2026, Microsoft updates Copilot Studio product terms to clarify how Query Data from Entra ID-authenticated use is handled when sent to Bing Search. Key commitments: Microsoft has no rights in Query Data beyond service provision, it’s not used to improve Bing or train AI models, and it’s treated as customer confidential information. No user experience or admin settings change—just added transparency.
🌐 Power Pages: Client APIs Are Here
MC1224376 – Control Power Pages components using client APIs, arriving February 28, 2026. No more fragile DOM manipulation or custom JavaScript workarounds. Use the JavaScript interface to control UI components, manage forms and lists, handle authentication, and query records with OData-compliant Web API methods.
Dynamically update UI elements and manage data without reloading the page.
🔐 Power Apps: Content Security Policy Enforcement
MC1218747 – Starting January 30, 2026, strict Content Security Policy (CSP) enforcement kicks in for Power Apps code apps (preview). Apps that call assets outside Power Apps domains get blocked by default. The app runs, but external assets don’t load.
Fix it: Allowlist required external sources using CSP configuration settings in PPAC. If you’re unsure what to allowlist:
- Toggle off “Enforce content security policy”
- Toggle on “Enable reporting”
- Test which sources need allowlisting after January 30th
- Add them to your allowlist
- Toggle enforcement back on
If your app doesn’t call external assets, leave CSP enforcement on and enable reporting mode to monitor policy violations.
💡 Bottom Line
This week delivered major changes across Power Platform. Tenant isolation enforcement, Power BI retirements, and new admin tools all hit in the next few weeks. If you haven’t reviewed your cross-tenant connections or started migrating away from Q&A, now’s the time.
The admin center upgrades—inventory, usage insights, Copilot tracking—give you real visibility into what’s happening in your environment. Power Automate debugging improvements and Copilot Studio enhancements make building and maintaining solutions easier.
Check the message center IDs above for full details on each update. And if you’re running code apps in Power Apps, get that CSP configuration sorted before January 30th.
Questions? Drop them in the comments. What update are you tackling first?
