MCP for D365 FO apps
Model Context Protocol (MCP) is an open standard (originally from Anthropic) that lets AI agents connect to real business data systems. Microsoft has now built an MCP server for D365 FO apps and it’s a big deal for anyone building AI agents on top of D365 FO. MCP Server – The server which holds all … Continue reading MCP for D365 FO apps
https://d365bits.com/2026/03/29/mcp-for-d365-fo-apps/
Published on: 1 hour ago
Power Apps Code App | Querying data Across Environments
In this article, let’s explore how to use a Power Apps Code App to fetch Dataverse data from a different Power Platform environment. This proof-of-concept uses Microsoft Dataverse connector’s “List rows from selected environment” action to query tables across environments. The full source code is available on GitHub — you can clone it, configure it for your environment, and deploy it […]
https://rajeevpentyala.com/2026/03/28/power-apps-code-app-querying-data-across-environments/
Published on: 13 hours ago
Dataverse Integration Patterns: Sync vs Async vs Event-driven (Real Use Cases)
As organizations start using Microsoft Power Platform, Microsoft Dataverse is no longer just a place to store data—it becomes a key part of how systems connect and work together.
For IT professionals and developers with experience in traditional integration, this often brings up important questions:
- Should the integration happen in real time (synchronous) or in the background (asynchronous)?
- When should we use event-driven design?
- How will these choices affect performance, reliability, and scalability?
Dataverse supports different integration approaches, such as:
- Real-time API calls (synchronous)
- Background processing (asynchronous)
- Event-driven integrations using messaging and automation tools
Each approach has its own purpose and trade-offs. Choosing the right one is important, because the wrong choice can lead to slow performance, unstable integrations, or limitations in the system.
Why Integration Patterns Matter in Dataverse (Before Choosing Tools)
When working with Microsoft Dataverse, a common mistake is to choose tools first—like Power Automate, Web API, or Azure Functions—without first understanding the right integration approach.
Microsoft recommends starting with integration patterns, because they directly impact how your solution performs, scales, and handles errors.
There are three main patterns:
- Synchronous – runs in real time and gives immediate results
- Asynchronous – runs in the background with some delay
- Event-driven – triggers actions based on events and keeps systems loosely connected
Each pattern serves a different purpose. For example:
- If users need instant feedback → use synchronous
- If some delay is acceptable → use asynchronous
- If multiple systems need to react to changes → use event-driven
Choosing the right pattern early is important because it affects:
- System performance
- Error handling
- Scalability
- User experience
In simple terms:
Integration patterns define the design of your solution, while tools are just used to implement it.
If you pick tools first without thinking about the pattern, the solution can become difficult to maintain and scale later.
1. Real‑time API calls (Synchronous)
Proposed Dataverse Features
- Dataverse Web API (OData v4)
- Organization Service / SDK (.NET, JavaScript – Xrm.WebApi)
- Synchronous Plug‑ins
- Custom APIs (synchronous execution)
Why These Fit
Microsoft Dataverse exposes a REST‑based Web API that supports full CRUD operations, metadata access, and custom actions. Calls are executed synchronously and the caller waits for a response, making this the correct option when:
- Immediate validation is required
- A user or external system expects an instant response
- The operation must participate in the Dataverse transaction pipeline
Synchronous plug‑ins and synchronous Custom APIs run inside the Dataverse execution pipeline, allowing real‑time business rule enforcement before data is committed.
Typical Use Cases
- Create/update records from external systems
- Validate data before save
- User‑initiated operations from apps or portals
2. Background processing (Asynchronous)
Proposed Dataverse Features
- Asynchronous Plug‑ins
- Dataverse Asynchronous Service (System Jobs / AsyncOperation)
- Dataverse Background Operations (via Custom APIs)
- Asynchronous Custom API execution
Why These Fit
Dataverse provides an asynchronous execution model for long‑running or non‑blocking operations. These operations:
- Execute outside the main transaction
- Do not block the user or API caller
- Are queued and executed when resources are available
The Dataverse Asynchronous Service processes system jobs such as async plug‑ins and workflows, improving scalability and system responsiveness. Newer Background Operations allow Custom APIs to run asynchronously with optional callbacks and retry handling.
Typical Use Cases
- Post‑save processing
- Bulk operations
- Heavy calculations
- Data enrichment
- Non‑critical downstream updates
3. Event‑driven integrations using messaging and automation tools
Proposed Dataverse Features
- Dataverse Business Events
- Dataverse Event Framework
- Webhooks
- Azure Service Bus integration
- Power Automate Dataverse triggers
Why These Fit
Dataverse has a robust event framework that allows business and system events to be published when data changes or actions occur. These events can be delivered to:
- Power Automate
- Azure Service Bus
- Azure Event Hub
- Webhooks
- Azure Functions / Logic Apps
Business Events allow organizations to expose high‑value, business‑level events (not just CRUD) and build loosely coupled, event‑driven architectures without polling. [learn.microsoft.com], [github.com]
Typical Use Cases
- Notify downstream systems when something happens
- Integrate with enterprise messaging platforms
- Trigger automation without blocking transactions
- Build scalable, decoupled integrations
Conclusion
Choosing the right Dataverse integration approach is less about the tools themselves and more about matching the pattern to the business need. Real‑time scenarios demand synchronous capabilities such as the Web API, SDKs, and synchronous plug‑ins to provide immediate feedback and enforce critical rules. Background workloads are best handled asynchronously using async plug‑ins, the async service, and background operations to protect user experience and system scalability. For modern, loosely coupled architectures, event‑driven features—Business Events, webhooks, Service Bus, and Power Automate triggers—enable systems to react independently and scale without tight dependencies. When these patterns are applied deliberately, Dataverse becomes not just a data platform, but a reliable integration backbone that balances responsiveness, resilience, and long‑term maintainability.
https://powerappbuilder.blogspot.com/2026/03/dataverse-integration-patterns-sync-vs.html
Published on: 15 hours ago
AI Won’t Replace You… But This Will (Real Truth About Jobs)
https://www.youtube.com/watch?v=9NIyF2GJ6wg
Published on: 16 hours ago
OnSelect – how to use for a clickable control in a gallery
Can the OnSelect property of a gallery conflict with that of a clickable control within? Learn a simple best practice to avoid the confusion!
The post OnSelect – how to use for a clickable control in a gallery appeared first on Hardit Bhatia: The Power Addict.
Published on: 1 day ago
Find it. Prioritize it. Fix it. #MicrosoftPurview #DataSecurity #Cybersecurity #DataProtection
https://www.youtube.com/shorts/ZInccvJ199s
Published on: 1 day ago
How to Use JSON Output in AI Builder Prompts for Structured Automation
If you’ve been working with AI in your business processes lately, you’ve probably run into a really frustrating roadblock: the gap between the chatty text an AI wants to give you and the structured data your automation actually needs. Let’s say you’re building a Power Automate flow to pull details out of customer emails. You… Read More »
The post How to Use JSON Output in AI Builder Prompts for Structured Automation first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
Published on: 1 day ago
Create an AI-Generated Color Theme in Power Pages Using Copilot
Gone are the days of manually picking hex codes and tweaking CSS variables for hours. Microsoft’s Copilot in Power Pages now lets you describe your brand in plain English — and watch a complete, polished color theme appear in seconds. This post walks you through exactly how it works, with real prompt examples and pro […]
Published on: 1 day ago
Planner tab support for Shared and Private Channels in Microsoft Teams
Microsoft Planner tabs will be supported in Microsoft Teams Shared and Private channels starting mid-May 2026. Users can add new or existing plans directly in these channels with inherited permissions and compliance controls. The feature is enabled by default, requires no admin setup, and maintains existing Planner behavior in standard channels. Introduction We are expanding Microsoft Planner integration in Microsoft Teams by enabling Planner tabs in Shared and Private channels. This change allows teams to plan and track work directly within the channel where collaboration occurs, including scenarios that require restricted membership or cross-organization collaboration. When this will happen: General Availability (Worldwide): Rollout begins mid-May 2026 and is expected to complete by late May 2026. How this affects your organization: Who is affected: Microsoft Teams users working in Shared or Private channels Microsoft 365 administrators managing Teams and Planner What will happen: Users can add Planner as a tab in Shared and Private channels using the + (Add a tab) experience. Users can create a new plan for the channel or add an existing plan associated with that channel. View image in new tab Planner inherits channel permissions and Microsoft 365 compliance controls. The feature is enabled by default and requires no admin configuration. There is no change to Planner behavior in standard channels. What you can do to prepare: No admin action is required. Update internal Teams and Planner documentation. Inform users that Planner is available in Shared and Private channels. Review governance policies related to Teams and Planner usage. Compliance considerations: Compliance area Explanation New customer data storage Users can create new Planner tasks and task comments in Shared and Private channels. This data is stored using existing Microsoft 365 Planner storage locations and retention policies. New communication pathways Users can communicate through Planner tasks and task comments within Shared and Private channels, including Shared channel scenarios. User self-service enablement Users can add Planner tabs to Shared and Private channels themselves, subject to existing Teams and app policies. Message ID: MC1262590
The post Planner tab support for Shared and Private Channels in Microsoft Teams appeared first on M365 Admin.
https://m365admin.handsontek.net/planner-tab-support-shared-private-channels-microsoft-teams/
Published on: 2 days ago
New M365 group creation and editing in My Groups
Microsoft 365 group creation and editing in My Groups will be enhanced by late March 2026, allowing owners to configure usage guidelines, email aliases, sensitivity labels, Exchange settings, and security options. The update improves control and clarity without impacting existing groups or requiring admin setup. Introduction We’re improving the Microsoft 365 group creation and editing experience in My Groups to give group owners more control and clarity from the start. The updated experience lets you configure key group, email, and security settings so your group works the way you expect. With this update, group owners can: Set group usage guidelines, email aliases, and sensitivity labels Configure Exchange settings such as sending welcome emails, subscribing members to conversations, and showing the group mailbox and calendar in Outlook Control who can send emails to the group, hide the group from the global address list, and allow or block external senders Enable security group functionality when needed This streamlined, self‑service experience helps ensure Microsoft 365 groups are created with the right defaults and policies. When this will happen: General Availability: We will begin rolling out in late March 2026 and expect to complete rollout by early April 2026. How this affects your organization: Who is affected: Users who are allowed to create or edit Microsoft 365 groups using My Groups Admins managing Microsoft 365 groups, Exchange Online, Microsoft Entra ID, and Microsoft Purview policies What will happen: Users / group owners: Users will see additional configuration options during Microsoft 365 group creation and editing in My Groups The experience provides greater visibility into how the group will behave once created or edited What you can do to prepare: No action is required to prepare for this change. If desired, admins can: Compliance considerations: Admins: There is no change to existing tenant‑level policies or controls All settings exposed during group creation continue to respect Microsoft Entra ID, Exchange Online, and Microsoft Purview configurations The feature is enabled by default and does not require admin configuration There is no impact to existing Microsoft 365 groups This update may reduce follow‑up support requests related to group […]
The post New M365 group creation and editing in My Groups appeared first on M365 Admin.
https://m365admin.handsontek.net/new-m365-group-creation-editing-groups/
Published on: 2 days ago
Microsoft Teams: Retirement of CAPTCHA for meeting join
Microsoft Teams will retire CAPTCHA for meeting joins by August 2026, replacing it with a default-on bot detection feature that requires organizer approval for bots. This ensures continuous bot protection without join friction. Tenant admins and organizers should review new policies but no immediate action is needed. Introduction Microsoft Teams is retiring CAPTCHA for meeting join to improve accessibility, reduce join friction, and modernize protections against automated participants. This change follows the release of a new, default‑on capability that detects external meeting assistant bots and provides organizers with increased visibility and control during the meeting join process, as previously announced in Message Center post MC1251206 (Microsoft 365 Roadmap ID 558107). To ensure a smooth transition: The new bot detection capability will be released and available to customers before CAPTCHA deprecation occurs. There will be no gap where meetings are left without baseline bot protection. CAPTCHA will be removed from meeting join flows and admin surfaces only after the new capability is fully in place. When this will happen Early May 2026: The Require verification by participants (CAPTCHA) policy will be locked and can no longer be enabled. Late July 2026: CAPTCHA policy removed from PowerShell. Late August 2026: CAPTCHA policy removed from the Teams Admin Center UI. Note: Dates are subject to change based on the release of bot identification (MC1251206/Roadmap ID 558107). How this affects your organization Who is affected Microsoft Teams tenant administrators Meeting organizers with anonymous or external participants What will happen What you can do to prepare Compliance considerations Admin control introduced: A new meeting policy governs how detected external bots are handled during meeting join. The CAPTCHA meeting policy will be retired and removed. CAPTCHA challenges will no longer appear during meeting join. A new, default‑on bot detection capability will provide baseline protection. Detected bots will require organizer approval to join meetings (recommended default). There will be no gap in bot protection during the transition. No immediate action is required. Review the new meeting policy when it becomes available in the Teams Admin Center. Keep the default setting that requires organizer approval for detected bots. […]
The post Microsoft Teams: Retirement of CAPTCHA for meeting join appeared first on M365 Admin.
https://m365admin.handsontek.net/microsoft-teams-retirement-captcha-meeting-join/
Published on: 2 days ago
Viva Engage: Community membership and experts management in iOS and Android for Engage and Engage app in Teams
Viva Engage is adding community membership and expert role management, plus verified-answer marking, to its iOS and Android apps (standalone and in Teams). These mobile features, rolling out March–April 2026, enable admins and experts to moderate and manage communities consistently without desktop access. We’re rolling out new community membership management and trusted‑answer capabilities in the Viva Engage mobile experience for iOS and Android, available in both the standalone Viva Engage app and the Viva Engage app in Microsoft Teams. These updates extend existing web functionality to mobile, enabling more consistent community governance and moderation across devices and allowing key actions to be completed without switching to a desktop experience. This message is associated with Roadmap ID 532722 and 537270. When this will happen: General Availability (Worldwide): Rollout begins late March 2026 and is expected to complete by late April 2026. How this affects your organization: Who is affected: Organizations using Viva Engage communities Community admins and designated experts Users accessing Viva Engage on iOS or Android (standalone app or within Microsoft Teams) What will happen: Community admins can manage community members directly from mobile, including adding or removing members Community admins can assign or remove community admin roles from mobile Community admins can assign or remove expert roles from mobile View image in new tab Eligible roles can mark verified answers from mobile devices View image in new tab Users will see community expert indicators and verified-answer indicators in conversations The feature is enabled by default and respects existing role-based permissions No tenant-level configuration or policy changes are required What you can do to prepare: No action is required to enable this feature Review current community admin and expert role assignments to ensure they align with your governance model Inform community admins and moderators that these moderation and role-management tasks are now available on mobile Update internal documentation or helpdesk guidance if you document Viva Engage moderation workflows Learn more: Learn more about Viva Engage | Microsoft Learn Introducing Community Experts in Viva Engage Introducing Verified Answers in Viva Engage Manage a community in Viva Engage | Microsoft Support Compliance considerations: […]
The post Viva Engage: Community membership and experts management in iOS and Android for Engage and Engage app in Teams appeared first on M365 Admin.
Published on: 2 days ago
Updated UX in Viva Connections on Teams mobile
Viva Connections in the Teams mobile app will update navigation from a three-tab layout to pill-based controls in April 2026. The change improves usability without altering functionality, is enabled by default, and requires no action, though internal documentation updates are optional. Introduction We’re updating the Viva Connections experience in the Microsoft Teams mobile app to provide a more modern, streamlined navigation that is easier to use across all devices. This update simplifies how users move between sections and improves discoverability, while keeping all existing functionality intact. When this will happen: General Availability (Worldwide): Rollout begins in early April 2026 and is expected to complete by late April 2026. How this affects your organization: Who is affected: All users who access Viva Connections in the Microsoft Teams mobile app (iOS and Android). What will happen: The Teams mobile Viva Connections experience will move from a three-tab layout (Dashboard, News, Resources) to a pill-based navigation model. Users will switch between Viva Connections sections using pill-shaped navigation controls at the top of the experience. In the News experience: The Unread and Saved for later pills will be replaced with: An Unread toggle A Saved for later button There is no change to functionality or content—only the navigation and layout are updated. The update is enabled by default and applies automatically. What you can do to prepare: No action is required to enable this update. Optionally, inform helpdesk staff and update internal documentation that references the previous navigation. Compliance considerations: No compliance considerations identified, review as appropriate for your organization. Message ID: MC1262585
The post Updated UX in Viva Connections on Teams mobile appeared first on M365 Admin.
https://m365admin.handsontek.net/updated-ux-viva-connections-teams-mobile/
Published on: 2 days ago
Microsoft Purview: Information Protection – Extended scoping capabilities for sensitivity label policies
Microsoft Purview Information Protection admins can now exclude modern Microsoft 365 groups and include dynamic, non-mail-enabled security groups in sensitivity label policies. This expands policy targeting flexibility without impacting users unless policies are updated. Rollout begins April 2026 with general availability in late May 2026. Introduction Purview Information Protection admins can now exclude modern Microsoft 365 groups and scope sensitivity label policies to dynamic and non-mail enabled security groups. These capabilities give admins more flexibility, expanding policy targeting beyond individual users and mail-enabled groups. This message is associated with Microsoft 365 Roadmap ID 558685. When this will happen: Public Preview: We will begin rolling out late April 2026 and expect to complete by mid-May 2026. General Availability: We will begin rolling out late May 2026 and expect to complete by late May 2026. How this affects your organization: Who is affected: Information Protection admins managing sensitivity label publishing policies What will happen: Admins can exclude modern Microsoft 365 groups from label publishing policies Admins can include non-mail-enabled security groups, including dynamic security groups Existing policies and configurations remain unchanged No user impact unless admins update policy scope What you can do to prepare: No action is required Optionally review and update label publishing policies to take advantage of expanded scoping Compliance considerations: Learn more: Create and publish sensitivity labels | Microsoft Learn (will be updated before rollout) Compliance question Explanation Does the change modify Information Protection labels or policy configuration capabilities? This update expands how sensitivity label publishing policies can be scoped by allowing admins to exclude modern Microsoft 365 groups and include non-mail-enabled security groups. Does the change include an admin control and can it be controlled through Entra ID group membership? Admins can scope sensitivity label publishing policies using non-mail-enabled security groups, including dynamic security groups in Microsoft Entra ID. Message ID: MC1262573
The post Microsoft Purview: Information Protection – Extended scoping capabilities for sensitivity label policies appeared first on M365 Admin.
Published on: 2 days ago
Microsoft Purview: Endpoint Data Loss Prevention – Device Health Reporting Dashboard
The Device Health Reporting Dashboard in Microsoft Purview offers admins a consolidated view of Endpoint DLP device health, policy sync status, activity, and Defender versions. Rolling out from May to June 2026, it enables quick issue diagnosis with no user impact and is enabled by default for eligible tenants. Introduction The Device Health Reporting Dashboard provides admins with a consolidated view of device health and policy sync readiness across all onboarded Endpoint Data Loss Prevention (DLP) devices. It surfaces at-a-glance insights into configuration health, policy sync status, device activity, and Microsoft Defender version distribution, helping admins quickly understand whether devices are healthy and ready to receive policy updates. With built-in drilldowns from summary graphs to device lists, the dashboard enables targeted investigation of unhealthy or non-compliant devices, such as devices that are offline, misconfigured, or running outdated Defender versions, so admins can diagnose issues and take remediation actions without leaving the reporting workflow. This message is associated with Microsoft 365 Roadmap ID 559267. When this will happen: Public Preview: We will begin rollout in late May 2026 and expected to complete by late May 2026 General Availability: We will begin rollout in late June 2026 and expected to complete by late June 2026 How this affects your organization: Who is affected: Microsoft 365 administrators managing Endpoint DLP in Microsoft Purview Organizations with onboarded Endpoint DLP devices What will happen: What you can do to prepare: No action is required. The Device Health Reporting Dashboard will be enabled automatically for eligible tenants. No additional configuration or onboarding steps are required. Once available, access the dashboard directly in the Microsoft Purview portal. Consider updating internal admin documentation or operational runbooks to reference the new reporting experience. Compliance considerations: Admins will see a new Device Health Reporting Dashboard in the Microsoft Purview portal. The dashboard provides at-a-glance insights into: Device configuration health Policy sync readiness Device activity and connectivity Defender version distribution Built-in drilldowns allow admins to navigate from summary charts to device-level lists for investigation. Admins can quickly identify devices that are offline, misconfigured, or running outdated Defender versions. The feature is […]
The post Microsoft Purview: Endpoint Data Loss Prevention – Device Health Reporting Dashboard appeared first on M365 Admin.
Published on: 2 days ago
Microsoft 365 Copilot: Updates to license request custom flow
Microsoft 365 Copilot will support custom license request policies by user group, enabling tailored guidance and routing aligned with internal approval workflows. Rolling out worldwide from late April to June 2026, admins can configure these policies in the Microsoft 365 admin center; existing setups remain unchanged unless updated. Introduction Microsoft is improving the custom license request experience for Microsoft 365 Copilot to help organizations better align Copilot license requests with their internal approval workflows. With this update, admins can create Copilot‑specific request policies and tailor guidance by user group, allowing more precise routing and clearer instructions for people requesting a license. When this will happen General Availability (Worldwide, DoD, GCC, GCC High): We will begin rolling out in late April 2026 and expect to complete by late June 2026. How this affects your organization Who is affected Users who request Microsoft 365 Copilot licenses Admins who configure license request policies in the Microsoft 365 admin center What will happen Admins will be able to create product‑specific custom license request policies for Microsoft 365 Copilot. Admins can scope policies by user group, such as security groups or Microsoft 365 groups. When someone requests a Copilot license, they will see: Admin‑defined instructions. A link to your organization’s internal approval workflow. License approvals will continue to occur outside Microsoft systems, using your existing internal processes. Existing custom license request behavior will remain unchanged unless an admin updates configuration. What you can do to prepare No action is required if you want to continue using your existing configuration. If you choose to adopt the new capabilities, you can: Learn more: Manage self-service license requests in the Microsoft 365 admin center | Microsoft 365 | Microsoft Learn Review your current custom license request policies in the Microsoft 365 admin center. Decide whether to apply product‑specific or group‑specific policies for Copilot. Confirm that internal approval links and instructions are accurate and accessible. Communicate these updates to your IT support or helpdesk teams. Compliance considerations No compliance considerations identified. Review as appropriate for your organization. Message ID: MC1262570
The post Microsoft 365 Copilot: Updates to license request custom flow appeared first on M365 Admin.
https://m365admin.handsontek.net/microsoft-365-copilot-updates-license-request-custom-flow/
Published on: 2 days ago
Create Excel spreadsheets from Copilot Notebook content
Copilot Notebooks will enable users with a Microsoft 365 Copilot (Premium) license to generate and edit Excel spreadsheets directly from notebook content. This feature rolls out in public preview from late March to April 2026 and general availability in late May 2026, with no admin action required. Introduction Copilot Notebooks enables users to generate Excel spreadsheets directly from the content and references collected in a notebook. Copilot creates a structured spreadsheet based on the notebook’s context, which can then be opened and edited in Excel. This capability streamlines the transition from ideas and source material into a usable spreadsheet by reducing manual setup and formatting. When this will happen: Public Preview via Frontier: Rollout begins in late March 2026 and is expected to complete by late April 2026. General Availability (Worldwide): Rollout begins in late May 2026 and is expected to complete by late May 2026. How this affects your organization: Who is affected: Users with access to Microsoft Copilot and Copilot Notebooks Organizations using Excel in Microsoft 365 A Microsoft 365 Copilot (Premium) license is required to use this feature What will happen: Users will be able to generate an Excel spreadsheet from content and references stored in a Copilot Notebook. View image in new tab The generated spreadsheet opens in Excel and can be edited like any other Excel file. The feature is enabled by default for eligible users. Existing Microsoft 365 security, compliance, and Copilot policies are respected. What you can do to prepare: Compliance considerations: No admin action is required. Review internal guidance or helpdesk documentation related to Copilot and Excel workflows. Consider notifying users that Copilot Notebooks can now generate Excel spreadsheets from notebook content. Learn more: Get started with Microsoft 365 Copilot Notebooks | Microsoft Support (will be updated before rollout) Compliance question Explanation Does the change alter how existing customer data is processed, stored, or accessed? Copilot processes existing content and references stored in a Copilot Notebook to generate a structured Excel spreadsheet. This processing occurs within Microsoft 365 services and respects existing security, compliance, and data residency boundaries. Does the change introduce or significantly […]
The post Create Excel spreadsheets from Copilot Notebook content appeared first on M365 Admin.
https://m365admin.handsontek.net/create-excel-spreadsheets-copilot-notebook-content/
Published on: 2 days ago
Power Platform admin center – Upcoming update to the enforcement of tenant isolation
Following customer feedback and support ticket evaluation, we have updated our tenant isolation enforcement policy. Starting March 30, 2026, only new tenants will have tenant isolation enabled by default. Additionally, existing tenants will not have their existing tenant isolation turned on if the option is blank as setup is opt-in. How does this affect me? Tenant isolation only applies to connectors running within a tenant. The default tenant isolation behavior will block all connection attempts from one tenant to another; inbound (connections to the tenant from external tenants), outbound (connections from the tenant to external tenants), or both (inbound – outbound) will be blocked by Power Platform. Communications within the same tenant will not be affected. In addition, users who sign in as guests (guest user access) will remain unaffected. What do I need to do to prepare? For existing tenants, we highly recommend enabling tenant isolation following the instructions outlined in Allow tenant isolation and configure the allow list. If you want to allow cross-tenant connections in Power Platform prior to the enforcement date, you can set up tenant isolation and explicitly allow individual tenants. Alternatively, you can disable tenant isolation entirely. If either of these actions are performed prior to March 30, 2026, your configuration will not be changed as part of the enforcement. For more information and to learn how to configure a tenant isolation policy, please review the Cross-tenant inbound and outbound restrictions documentation. Message ID: MC1262537
The post Power Platform admin center – Upcoming update to the enforcement of tenant isolation appeared first on M365 Admin.
Published on: 2 days ago
New resources to help organizations prepare for Secure Boot certificate expirations
Secure Boot certificates begin expiring in June 2026, and IT admins should take action now to help ensure devices remain secure. Timely deployment of updated certificates is essential to preserving device startup integrity and avoiding servicing (i.e., updates) disruptions. New guidance has recently been published to support a range of deployment scenarios. Whether your organization manages certificates through Microsoft Intune, Group Policy, or manual processes, the resources below provide detailed steps, recommended practices, and troubleshooting guidance to help you plan your updates: Updates and announcements – This page consolidates ongoing updates, milestones, and rollout status changes for the deployment of new Secure Boot certificates across Windows devices. Use it to stay current on important servicing communications as the deployment progresses. Sample Secure Boot E2E Automation Guide – This guide provides an end-to-end view of the PowerShell‑based automation system for deploying Secure Boot certificate updates using Group Policy to domain-joined machines in a controlled, graduated manner. It includes details, examples, and operational guidance for domain‑joined environments. A Closer Look at the High Confidence Database – This article explains how Secure Boot confidence levels are calculated, how data is evaluated and published, and how Windows servicing uses this information to determine certificate deployment readiness. It’s designed for IT pros, security teams, and support engineers who need deeper insights into certificate evaluation. When will this happen: These resources are available now. IT admins should begin reviewing the new guidance and complete certificate update planning and deployment activities as soon as possible to ensure devices remain protected and to avoid servicing or startup disruptions. Secure Boot certificate expiration begins in June 2026. How will this affect your organization: Devices that do not receive the updated Secure Boot certificates before expiration may encounter startup integrity issues or Windows servicing interruptions. The new resources provide guidance for organizations using Microsoft Intune, Group Policy, or manual processes and help ensure devices are fully prepared for upcoming certificate changes. What you need to do to prepare: Begin developing and executing your Secure Boot certificate update strategy as soon as possible. Review the newly published resources to determine the […]
The post New resources to help organizations prepare for Secure Boot certificate expirations appeared first on M365 Admin.
Published on: 2 days ago
The March 2026 Windows non-security preview update is now available
The March 2026 non-security preview update is now available for Windows 11, versions 26H1, 25H2, and 24H2. Information about the contents of this update is available from the release notes, which are accessible from the Windows 11 update history page. To learn more about the different types of monthly quality updates, see Windows monthly updates explained. Looking to explore upcoming features and improvements in Windows 11? Check out the Windows roadmap. It includes what’s coming to the Windows Insider Program, what’s gradually rolling out, and what’s generally available. Highlights for the Windows 11, version 25H2 update: Narrator now provides rich image descriptions on Copilot+ PCs and works with Copilot on all Windows 11 devices, allowing users to get instant on‑device descriptions or ask Copilot for more detail. This update improves the design of the dialog boxes in Settings > Accounts > Other users to match the modern Windows look and support dark mode. The visibility of the dialog box option depends on whether the device has a domain joined work or school account. This update improves the File Explorer experience, including more reliable unblocking of downloaded files and support for Voice Typing when renaming files. This update delivers several display improvements, including support for refresh rates above 1000 Hz, improved auto‑rotation and HDR reliability, and better power efficiency for USB4‑connected monitors during sleep. For instructions on how to install this update, see the KB for your operating system listed below: Windows 11, version 26H1: KB5079489 Windows 11, versions 25H2 and 24H2: KB5079391 Message ID: MC1262522
The post The March 2026 Windows non-security preview update is now available appeared first on M365 Admin.
https://m365admin.handsontek.net/march-2026-windows-non-security-preview-update-now-available/
Published on: 2 days ago
Microsoft Copilot Studio – Analyze user sentiment from agent conversations
We are announcing the ability to analyze user sentiment from agent conversations in Microsoft Copilot Studio. This feature will reach general availability on March 31, 2026. How does this affect me? Copilot Studio uses AI models to analyze the tone, language, and user interactions throughout the conversation to calculate an overall sentiment score. The new sentiment analysis is an additional metric to understand customer satisfaction. Sentiment analysis works alongside existing CSAT scores and will help you quickly identify sessions with negative sentiment, enabling you to investigate issues and continuously improve your agent’s performance with the following features: Analyze a sample of all sessions. Automatic availability for customers with at least 10 sessions with questions that have triggered generative answers in the past 7 days. Sentiment is calculated for each user message in the sampled sessions and then all messages are aggregated for a single sentiment score for the session. Each session is classified as positive, negative, or neutral, based on all user messages within that session. The sentiment score is calculated and refreshed once a day. What action do I need to take? This message is for awareness, and no action is required. Message ID: MC1262498
The post Microsoft Copilot Studio – Analyze user sentiment from agent conversations appeared first on M365 Admin.
Published on: 2 days ago
Microsoft Dataverse – Restore deleted Dataverse records within a specified timeframe
We are announcing the ability to restore Dataverse table records within a specified timeframe from any type of delete scenario. This feature will reach general availability on April 27, 2026. How does this affect me? With the ability to restore deleted records with a configurable retention period of up to 30 days in Microsoft Dataverse, you gain greater control and resilience in your data management processes, reducing the risk of permanent data loss. This feature includes the following capabilities: Comprehensive recovery: Restore deleted records regardless of deletion type, including manual, automated, single, multiple, or bulk. Flexible access: Restore data through both the Dataverse user interface and APIs/SDK. Configurable retention: Define how long deleted records remain available for recovery Admin-controlled enablement: Administrators must enable the feature at the environment level to take advantage of recovery capabilities. What action do I need to take? This message is for awareness, and no action is required. If you would like more information about this feature, please visit: Restore deleted records within a specified timeframe Safeguard, Restore, and Manage Deleted Records in Microsoft Dataverse – Microsoft Power Platform Blog Message ID: MC1262302
The post Microsoft Dataverse – Restore deleted Dataverse records within a specified timeframe appeared first on M365 Admin.
Published on: 2 days ago
OneDrive: Discover Copilot actions in File Preview
See what Copilot can do the moment you preview a file in OneDrive or SharePoint. Ready-to-use prompts appear alongside the Copilot button, helping you summarize documents, generate FAQs, and more — all without writing a single prompt. Product SharePoint Release phase General Availability Release date April CY2026 Platform Web Cloud Instance Worldwide (Standard Multi-Tenant) Created 2026-03-26 23:15:28Z Roadmap ID 559481 Roadmap Link https://www.microsoft.com/microsoft-365/roadmap?id=559481
The post OneDrive: Discover Copilot actions in File Preview appeared first on M365 Admin.
https://m365admin.handsontek.net/onedrive-discover-copilot-actions-file-preview/
Published on: 2 days ago
Microsoft Teams: Enhanced media quality for Direct Guest Join
You’ll notice media quality improvements including support for up to 16 participant videos (4×4 grid) and simulcast streaming when using Direct Guest Join. These updates make cross platform meetings more immersive and reliable when joining Teams meetings from Zoom, Google Meet, or Cisco devices. Product Microsoft Teams Release phase General Availability Release date May CY2026 Platform Cloud Instance Worldwide (Standard Multi-Tenant) Created 2026-03-26 23:15:28Z Roadmap ID 558922 Roadmap Link https://www.microsoft.com/microsoft-365/roadmap?id=558922
The post Microsoft Teams: Enhanced media quality for Direct Guest Join appeared first on M365 Admin.
https://m365admin.handsontek.net/microsoft-teams-enhanced-media-quality-direct-guest-join/
Published on: 2 days ago