Enable Dataverse /mention in Microsoft 365 Copilot: Environment and App Labels for Records

Microsoft has addressed this exact friction point by launching enhanced Microsoft Dataverse record descriptions for the /mention experience in Microsoft 365 Copilot. Tracked under AI at Work Roadmap ID 576788 (and associated with Microsoft 365 Message Center notice MC1428623, as indexed by change-intelligence tracker DeltaPulse), the update enriches the Context IQ picker so end users see descriptive labels containing environment, app, and table information when referencing Dataverse, Dynamics 365, and Power Apps records. Following a July 2026 preview window and an August 2026 general availability rollout across Worldwide (Standard Multi-Tenant) web instances, the feature is now officially marked as launched.

What Changed in the Context IQ Picker​

Before we look at the admin switches, it helps to understand how /mention fits into daily Microsoft 365 workflows. Historically, sharing a line-of-business record meant leaving Outlook or Teams, opening a Dynamics 365 or Power Apps browser tab, hunting down the record, copying its URL, and pasting it back into your message. The /mention integration via Context IQ streamlined this by letting users type / followed by the first few characters of a recently viewed record right inside their productivity apps or Copilot Chat.

However, in complex Power Platform deployments, a bare record name rarely tells the whole story. According to Microsoft Learn's Power Platform release plan documentation, the update enhances Dataverse, Dynamics 365, and Power Apps references inside Context IQ by surfacing environment, app, and table information. Meanwhile, Microsoft Learn's administrative guide on linking business records specifies that each record displays an enhanced label structured around Environment Name + App Name + Record Name, noting that if a user views the same record across multiple applications, the label reflects the most recently used app.

Whether a user is distinguishing between a staging environment and production, or telling an Account row apart from a custom Project table row that happens to share the same title, that extra metadata acts as a crucial visual guardrail before the user commits to the selection.

Summary of the Release​

Section Summary: The update upgrades the Context IQ / record picker in Microsoft 365 Copilot from generic titles to context-rich labels showing environment, application, and table provenance, reducing selection errors across multi-app tenants.

How to Enable Dataverse /mention in Power Platform​

This capability is not forced onto every environment out of the box; Microsoft lists it as enabled for end users by admins, makers, or analysts. To make recently viewed Dataverse and Dynamics 365 records selectable via /mention in Microsoft 365 apps, administrators must flip an environment-level toggle in the Power Platform admin center.

According to Microsoft Learn's administrative documentation, here is the exact procedure:

1. Sign in to the Power Platform admin center.
2. In the navigation pane, select Manage, and then select Environments.
3. Choose the target environment from the Environments page.
4. On the command bar, select Settings.
5. Expand Product, and then select Features.
6. Locate the Search section and toggle on Search for records in Microsoft 365 apps.
7. Select Save to apply the configuration.

How End Users Put It to Work​

Once enabled, the workflow spans Outlook on the web, Copilot Chat, Researcher, Word, and Teams:

• In Outlook on the web: Users can either type / directly into the body of a new email to insert a rich record link for a colleague, or ask Copilot in Outlook to draft an email referencing /account data.
• In Copilot Chat, Word, and Teams: Users type / followed by the beginning of a record's name (such as /Contoso account or /Adatum Corporation) and select the right item from the suggested list. Copilot then uses that record as context to draft status updates in Word, generate meeting agendas in Teams, or answer prompt questions like showing closed opportunities for that account.

Section Summary: Administrators control availability per environment via the "Search for records in Microsoft 365 apps" setting in the Power Platform admin center, unlocking / record references across Outlook on the web, Word, Teams, Researcher, and Copilot Chat.

Governance, Security, and Technical Caveats​

From an enterprise IT perspective, a convenience feature is only as good as its security and compliance posture. Whenever line-of-business data bridges into Microsoft 365 productivity tools, administrators rightly ask where the data lives, who can see it, and what its real-world limitations are. Microsoft Learn's documentation outlines four critical boundaries every Power Platform and Microsoft 365 admin should factor into their rollout plan:

1. Cross-Service and Multi-Geo Metadata Synchronization​

Enabling this feature initiates a lightweight background synchronization between Dataverse and Microsoft 365. Specifically, Microsoft documents that the environment name, app name, record name, and a link to the most recently used record sync across to Microsoft 365.

• The compliance catch: This sync crosses service and compliance boundaries between Power Platform and Microsoft 365, and in multi-geo organizations, it may cross geographic boundaries if a user's Dataverse environment resides in a different region than their Microsoft 365 mailbox or storage. Any updates or deletions made to the synced data in Dataverse are reflected by updating or deleting the corresponding record information in Microsoft 365.

2. Zero Permission Escalation​

Inserting a record via /mention does not magically grant the recipient access to the underlying business data. First, a user's / picker only surfaces records that the user personally has permission to view and has most recently used. Second, if that user drops a record link into an Outlook email, the recipient can only open it if they already possess access to the target Power Platform environment, hold the required security roles, and have permission to view that specific record.

3. The 15-Minute Indexing Window​

If you are testing this feature right after flipping the admin switch—or if a user just opened a brand-new client account in Dynamics 365 and immediately jumps over to Outlook on the web to /mention it—don't panic if the record doesn't appear right away. Microsoft notes that it can take up to 15 minutes after viewing a record in Dynamics 365 or a model-driven app before that record becomes available to /mention in Microsoft 365 Copilot Chat inside productivity apps.

4. The Researcher Live-Data Boundary​

While users can select a recently viewed Dataverse or Power Apps record via / inside Microsoft 365 Researcher (for example, prompting Researcher to "Prepare a market analysis for /Contoso account"), there is an architectural distinction in how Researcher handles that reference. Microsoft Learn explicitly notes that Researcher currently uses the selected record as contextual grounding to gather and synthesize information from the web and the user's Microsoft 365 productivity data (emails, files, meetings, and chats). Researcher does not currently retrieve or reason over live Dynamics 365 or Power Apps data tied to that referenced record.

Section Summary: While richer labels improve usability, admins must account for cross-service and potential multi-geo syncing of record names and links, a 15-minute sync delay after viewing a record, strict inheritance of existing Dataverse security roles, and the fact that Researcher uses /mention records for M365/web grounding rather than querying live Dataverse fields.

Why Small UI Tweaks Matter for Enterprise AI​

It is easy for flashy model upgrades and autonomous agent announcements to steal all the oxygen in the AI room. Yet in day-to-day enterprise IT, adoption often hinges on much more mundane plumbing: can a user trust that the AI assistant is looking at the exact database row they think it is?

By bringing environment, app, and table context directly into the Context IQ /mention flyout, Microsoft removes a subtle but persistent source of user error for organizations running multiple Power Platform environments and model-driven apps. Combined with Microsoft's broader transition—where new Dynamics 365, Power Platform, and Dataverse capabilities are now tracked directly on the unified AI at Work roadmap rather than isolated release plans—it underscores how tightly Dataverse is being woven into the everyday Microsoft 365 Copilot fabric. For admins, the path forward is clear: verify your multi-geo compliance stance on synced record metadata, flip the feature switch on the environments that matter, and let your users stop playing guessing games with duplicate record names.