Tell us about your PDF experience.

Microsoft Power Platform

documentation
Discover how to make the most of Microsoft Power Platform products with online training
courses, docs, and videos covering product capabilities and how-to guides. Learn how to quickly
and easily build AI-driven agents with Copilot Studio, custom apps using Power Apps, automate
workflows to improve business productivity using Power Automate, analyze data for insights
using Power BI, and rapidly design, configure, and publish modern websites using Power Pages.

W H AT ' S N E W TRAINING
What's new in Power Platform? Power Platform training and
certifications

GET STARTED VIDEO

Power Platform In a Day Power Platform videos
workshops

Power Platform products

Use Microsoft Power Platform to build AI-driven agents using Copilot Studio, apps using Power Apps,
automate tasks using Power Automate, analyze data using Power BI, and create websites using Power
Pages.

Copilot Studio Power Apps Power Automate

Copilot Studio Power Apps documentation Power Automate
documentation documentation
Power Apps training
Copilot Studio training Power Automate training
Power Apps videos
Copilot Studio videos Power Automate videos
 Power BI Power Pages
Power BI documentation Power Pages documentation
Power BI training Power Pages training
Power BI videos Power Pages videos

Power Platform capabilities

Enhance apps and business processes with AI Builder, connect to a variety of data sources through
Connectors, use Copilot and generative AI capabilities to boost productivity, use powerful data service
to quickly build enterprise-grade apps with Dataverse, and use low-code strongly-typed declarative and
functional language with Power Fx.

Copilots and
AI Builder Connectors
generative AI

Microsoft Dataverse Power Fx

Power Platform administration, development, and

guidance

Administration Application lifecycle Guidance

Learn about how to administer management (ALM) guide Use the Power Platform
using Power Platform admin Learn how to implement ALM guidance center for adoption
center using Power Platform products best practices, Center of
and services Excellence (CoE) kit, white…
 Extend and develop Architecture Center Well-Architected
Learn about developing apps Guidance for architecting Guiding principles, strategies,
and services in Power Platform solutions with Power Platform and tools to help make
using code and Copilot Studio using informed decisions about the
established patterns and best… design, planning, and…

Related products and capabilities

Dynamics 365 Microsoft Azure

The next generation of CRM Ever-expanding set of cloud
and ERP applications computing services to help
your organization meet its
business challenges
Microsoft Power Platform admin
documentation
Use Power Platform admin center to manage environments and settings for Power Apps, Power
Automate, Power Pages, Microsoft Copilot Studio, and customer engagement apps.

Get started

ｅ OVERVIEW

Overview of the Power Platform admin center

Power Platform licensing

Dataverse capacity-based storage details

Sign in to Dynamics 365 and Office apps

Use the new and improved Power Platform admin center

Create and manage environments

ｐ CONCEPT

Environment management capabilities

Power Platform environments overview

Automatic deletion of Power Platform environments

General availability deployment

ｃ HOW-TO GUIDE

Create and manage environments

Change the environment type

Opt in to early access updates

Manage security and users

ｐ CONCEPT
Security overview

Security roles and privileges

Data protection and privacy

Identity and access management

Compliance

ｃ HOW-TO GUIDE

Create and manage users

Create or edit a security role to manage access

Copilot

ｐ CONCEPT

Copilots and generative AI in Power Platform

Responsible AI FAQs for Microsoft Power Platform

ｃ HOW-TO GUIDE

Move data across regions for Copilots and generative AI features

Track, manage, and scale Copilot adoption

View agent inventory (preview)

Troubleshoot

ｃ HOW-TO GUIDE

Get support

Check online service health

View troubleshooting content

Learn
ｄ TRAINING

Work with Microsoft Power Platform tenants, environments, subscriptions, and Dynamics 365 apps

Use best practices to secure and govern Microsoft Power Platform environments
Application lifecycle management (ALM)
with Microsoft Power Platform
Learn how to implement application lifecycle management (ALM) using Microsoft Power
Platform (Power Apps, Power Automate, Microsoft Dataverse, Microsoft Copilot Studio).

About ALM with Power Platform

ｅ OVERVIEW

What is ALM?

ｐ CONCEPT

ALM basics with Power Platform

Environment strategy

ｉ REFERENCE

Tools and apps used for ALM

Understand and work with solutions

ｐ CONCEPT

Solution concepts

Understand solution layers

Use solutions to customize

Segment solutions

Implement healthy ALM

ｐ CONCEPT

Scenario 0: ALM for a new project

Scenario 1: Citizen development ALM

Scenario 2: Moving from a single environment

Scenario 3: Moving from unmanaged to managed solutions

Scenario 4: Use DevOps for automation

Scenario 5: Support team development

Scenario 6: Embrace citizen developers

For developers

ｐ CONCEPT

ALM for developers

Work with solution components

Solution and packaging tools

Manage solutions using custom code

ALM automation

ｅ OVERVIEW

Use Power Platform Build Tools for Azure DevOps

Use GitHub Actions for Power Platform

Deploy solutions using pipelines

CoE: Set up ALM Accelerator

CoE: Use ALM Accelerator

Related docs

ｅ OVERVIEW

Create apps in Power Apps

What is Microsoft Dataverse?

Work with solutions

Power Platform admin guide

Power Platform Center of Excellence (CoE) Kit

Best practices and guidance when using Microsoft Dataverse

Microsoft Power Platform developer
documentation
Learn how to extend Microsoft Power Platform using code first components and integrating
with back-end services.

Get started

ｅ OVERVIEW

Power Platform for developers

ｃ HOW-TO GUIDE

Create a developer environment

ｄ TRAINING

Introduction to developing with Power Platform

Fusion development

ｐ CONCEPT

Fusion development

ｉ REFERENCE

Fusion development ebook

ｄ TRAINING

Transform business apps with fusion development

ALM for developers

ｉ REFERENCE

Power Platform ALM basics

Build Tools for Azure DevOps

GitHub Actions

Power Platform CLI

Create packages using Package Deployer

Work with solutions using SDK

For ISVs

ｃ HOW-TO GUIDE

Publish your app on AppSource

Tools for Developers

ａ DOWNLOAD

Power Platform CLI

Power Platform Tools for Visual Studio

ALM developer tools

Dataverse developer tools

Visual Studio connected service

Dataverse

ｉ REFERENCE

Dataverse developer docs

Plug-ins

Webhooks

Custom APIs

Virtual tables
Power Apps

ｉ REFERENCE

Canvas apps developer docs

Model-driven apps developer docs

Power Apps component framework

Custom connectors

JavaScript and the Client API

Code apps (preview)

ｆ QUICKSTART

Create a Canvas App front end for your [Link] web API (Preview)

Power Automate

ｉ REFERENCE

Custom connectors

Use workflow definition functions

Use APIs with desktop flows

Power BI

ｉ REFERENCE

Custom visuals

Use Power BI REST APIs

Analysis Services developer documentation

Copilot Studio
ｉ REFERENCE

Bot Framework Composer

Power Pages

ｉ REFERENCE

Custom page layouts

Work with Liquid templates

Power Pages Web API

Use Visual Studio Code and Power Platform CLI

Use code components

 Microsoft Power Platform guidance
documentation
Provides information to help you create and implement the business and technology strategies
necessary for your organization to succeed with Microsoft Power Platform.

Power Platform adoption guidance

Find guidance for each phase of your Power Platform adoption journey.

Strategy Plan
Assess Power Platform adoption strategy Define roles and responsibilities
Define vision, metrics and goals Evaluate delivery models
Measure and communicate business value Establish license assignment strategies
More... More...

Security Governance
Enhance your security posture Management at scale
Establish data protection and privacy controls Establish an environment strategy
Configure identity and access management Implement reactive governance controls
More... More...

Operations Availability
 Establish effective ALM practices Plan mission critical workloads
Gain insights into Power Platform adoption Build a disaster recovery plan
Monitor license and capacity consumption More...
More...

Readiness Community
Establish a training and upskilling strategy Define community purpose and goals
Set up tools to support your community Onboard new makers
Host internal training events Share success stories
More... Nurture and educate

Tools and resources

Power Platform toolkits Real-world case studies More...

Center of Excellence Starter Kit A1 Inteligencia em Viagens White papers
overview boosts team efficiency
Power Platform icons
Business value toolkit Epiq streamlines employee
onboarding
Creator Kit overview
Degrees of Change automates
More...
nonprofit operations
More...

Related guidance centers

Guidance information focused on individual Power Platform components

Power Apps guidance Power Automate Power Pages guidance

guidance
Power Apps coding guidelines Architecture white paper
Power Apps patterns Power Automate coding Security white paper
guidelines
Planning a Power Apps project More...
Plan a Power Automate project
 Collaborating and co- RPA with SAP
developing apps
Automation Kit
More...
More...

Microsoft Copilot Power Platform Well- Power Platform and

Studio guidance Architected guidance Copilot Studio
Architecture Center
Topics best practices What is Power Platform Well-
Architected? Welcome to the Architecture
Trigger phrases best practices
Power Platform Well- Center
Measuring chatbot
Architected pillars Architecture key concepts
engagement
Implementing Browse reference architectures
More...
recommendations
More...
More...

Documentation
Official documentation for Power Platform components

Power Apps docs Power Automate docs Power BI docs

Quickly build low-code apps Create automated workflows Turn your unrelated sources of
that modernize processes and between your favorite apps data into coherent, visually
solve tough business and services to synchronize immersive, and interactive
challenges in your organizati… files, get notifications, collect… insights.

Power Pages docs Microsoft Copilot Studio Power Platform admin

Design, host, and administer docs docs
secure, modern, and low-code Create powerful bots using a Use Power Platform admin
business websites. guided, no-code graphical center to manage
interface without the need for environments, security,
data scientists or developers. features, and settings for…
Microsoft Dynamics 365 and Power
Platform data residency documentation
10/13/2025

The purpose of this document is to provide comprehensive information about data residency
and customer data storage for Dynamics 365 and Power Platform.

Overview
Microsoft Dynamics 365 and Power Platform are integrated cloud solutions that help
organizations analyze data, automate workflows, and build intelligent agents. Dynamics 365
delivers enterprise-grade CRM and ERP capabilities. Power Platform empowers users to create
low-code apps, automate processes, and gain insights.

Products covered
This document encompasses the Dynamics 365 and Power Platform products outlined below.

Dynamics 365
Microsoft Dynamics 365 Sales

Microsoft Dynamics 365 Customer Service

Microsoft Dynamics 365 Field Service

Microsoft Dynamics 365 Finance

Microsoft Dynamics 365 Supply Chain Management

Microsoft Dynamics 365 Intelligent Order Management

Microsoft Dynamics 365 Commerce

Microsoft Dynamics 365 Business Central

Microsoft Dynamics 365 Project Operations

Microsoft Dynamics 365 Human Resources

Microsoft Dynamics 365 Customer Insights

 Microsoft Dynamics 365 Project Service Automation

Microsoft Dynamics 365 Guides

Microsoft Dynamics 365 Contact Center

Microsoft Dynamics 365 Remote Assist

Microsoft Dynamics 365 Customer Voice

Power Platform
Power Automate

Power Apps

Power Pages

Copilot Studio

Other
Microsoft 365 Copilot for Sales

Where your Microsoft Dynamics 365 and Power

Platform customer data is stored
Customer data for Microsoft Dynamics 365 and Power Platform is stored in Microsoft Azure
datacenters located in various geographic regions around the world. Customers can choose
the region (also referred to as "geo") where their customer data will be stored.

Microsoft may replicate customer data to other regions within the same geo for data
durability, except where otherwise specified.

Regions where Microsoft Dynamics 365 and Power

Platform can be deployed
Explore service availability and deployment regions in Dynamics 365 and Power Platform
Availability Reports .

７ Note
 Because there is only one region in Brazil, customer data in Brazil South may be
replicated to South Central US (Texas) for disaster recovery purposes.

For China-specific information, learn more here .

Storing customer data at rest in geo

Microsoft will store customer data at rest in the selected Azure geographic location (geo) for
Dynamics 365 and Power Platform products except when:

It is necessary for Microsoft to provide customer support, troubleshoot the service, or

comply with legal requirements.

Customers use services that are designed to operate globally, including the following
services:

Dynamics 365 and Power Platform home page and admin center portals, which store
application names, descriptions, and logos globally for performance.

Entra ID which may store Active Directory data globally.

You can find more information here.

Azure Multi-Factor Authentication, which may store multi-factor authentication data

globally.
You can find more information here.

Customer data collected during the onboarding process by the Microsoft 365 Admin
Center.
You can find more information here .

Content Delivery Network (CDN), which provides a global caching service and stores
customer data at edge locations around the world.

Dataverse table and column names (formerly called entity and field names) are
replicated globally for support and troubleshooting purposes, but the content within
those database tables remains stored in geo.

Services that provide global routing functions and do not process or store customer
data. This type of service includes Azure DNS, which provides domain name services
that route to different regions.

Preview, beta, or other pre-release services, which typically store customer data in the
United States but may store it globally.
 Customers use features that are powered by Microsoft 365 services as described in
product documentation. For these features, data will be transferred to Microsoft 365
services and governed by Microsoft 365 terms and data residency commitments.

Customers may also configure external services to extend Dynamics 365 products and
Power Platform functionality. These configurations may cause customer data to be
transferred outside of the selected geo. Examples include:

Machine Learning Cognitive Services: If features using cognitive services are activated,
customer data for domains such as product recommendations and demand
forecasting may be synchronized outside of the configured region. Use of these
features is optional. You can find more information here.

Data integration: When using Dynamics 365 or Power Platform to work with external
services (Microsoft or third-party), customer data may be transferred outside the
configured production environment to a geographic location designated by the
customer.
Microsoft Power Apps, and Microsoft Power Automate: When connected to
Dynamics 365 products, customer data may be sent outside of the designated region
to where these services are deployed.

Azure Dev Ops: Customers can choose where to store custom code, metadata, and
data assets that support their Dynamics 365 implementation. You can find more
information about the availability of Visual Studio Team Services here.

Microsoft Dynamics Lifecycle Services: The administration portal stores certain

customer data on servers located in the United States such as:

Your code or metadata, and data packages (for example, master or application
configuration data) to support application lifecycle;

Business process models and task guides;

Usage and diagnostic logs during the application lifecycle process; and Content
related to support requests submitted to Microsoft such as support issues, service
requests, and hotfix requests.

Additionally, certain types of customer data specifically the application name,

application description, and application logo will be stored globally.

Regardless of where the customer data is stored, Microsoft does not control or restrict the
locations from which customers, or their end users, may access customer data.

The following products contain additional product-specific scenarios where customer data may
be stored outside the selected geo. These variations reflect distinct features or positioning
relevant to each service.

Product-specific considerations
ﾉ Expand table

Product Key variation

Dynamics 365 Email and content delivery may operate globally. Custom schema/display names may
Customer Insights be referenced globally, but field values remain in-geo.

Dynamics 365 Electronic invoicing may involve cross-geo transfers.

Finance

Dynamics 365 CSU data syncs to the production instance. Fraud Protection may process data
Commerce globally.

Dynamics 365 Provisioning service stores environment lists in the US. Teams integration may
Human Resources transfer data to the Teams service region.

Power Pages Website name and URL are stored globally.

Copilot Studio If tenant location is not listed, data is stored in the US; for France, data is stored in
Europe. External configurations (for example, Customer Service hand-off, Facebook,
Teams) may transfer data.

Dynamics 365 Use of Azure Communication Services for telephony and messaging purposes. In this
Contact Center case, customers do have the ability to choose the location where transcription and
recordings are temporarily stored. The permanent storage of this data still resides in
the geo where the Contact Center operates.

Dynamics 365 Calling and collaboration features may send customer data to the geo where
Remote Assist customer’s Teams service is deployed.
and Guides

Additional resources
Microsoft Trust Center: Cloud Data Integrity and Compliance | Microsoft Trust Center
Important changes (deprecations) coming
in Power Platform
The announcements and deprecations described in this article apply to Power Apps and Power
Automate. Admins and IT professionals can use this information to prepare for future releases.
This article was first published on June 27, 2017.

For deprecation information of other products, see Other deprecation articles later in this
article.

） Important

"Deprecated" means we intend to remove the feature or capability from a future release.
The feature or capability is fully supported until it's officially removed. This deprecation
notification can span a few months or years. After removal, the feature or capability will no
longer work. This notice is to allow you sufficient time to plan and update your code
before the feature or capability is removed.

Deprecation of the classic look for model-driven

apps
Starting in April 2026, makers will no longer be able to switch to the classic look in model-
driven apps. All apps will use the modern, refreshed look by default.

Why is this needed?

We are standardizing the experience across model-driven apps to deliver a consistent,
accessible, and modern interface that ensures customers benefit from ongoing user experience
improvements while unlocking AI-powered capabilities available only in the modern look.

Impact
There is no impact on app logic, data, or permissions. Existing apps will automatically display
the modern look. The admin settings related to this feature will be removed.

Replacement feature
The modern, refreshed look is now the default experience for all model-driven apps. No action
is required from makers or admins. For more information on this, see Modern, refreshed look
for model-driven apps.

Deprecation of create an app from an image or

Figma file
Starting October 21, 2025, makers will no longer be able to create new apps using the An
image or Figma file option in Power Apps.

Why is this needed?

We are bringing new capabilities to help you create apps such as plans and generative pages.

Impact
There is no impact on existing apps created using an image or Figma file and will continue to
be supported.

Replacement feature
Plans and generative pages can be used to create apps. Makers can also use third-party and
community tool plugins to bring external designs into Power Apps.

Deprecation of the format data by examples

feature in Power Automate
As of the first week of August 2025, the format data by examples feature in the Power
Automate classic designer is deprecated. The feature was available worldwide and used the
PROSE model to help makers write expressions for a specific use case of formatting a piece of
data in a flow to another permissible data type.

Why is this needed?

With Copilot, we developed a new feature to help you create and update expressions using
natural language better and easier.

Impact
The deprecation has no impact to customers who have used the feature to write data
formatting expressions. Going forward, the feature is hidden.

However, users are no longer able to format dates, numbers, and text using examples in the
Power Automate classic designer.

Replacement feature
The expression assistant feature in the expression editor can be used as a replacement to the
format data by example feature. Learn how to use the expression assistant feature (including a
video) in Create, update, and fix expressions with Copilot expression assistant (preview).

Deprecation of Viva Engage (Yammer) connector

support for open authorization connections
Starting September 1, 2025, the Viva Engage connector will no longer support OAuth 2.0 (open
authorization) connections. New connections must use Entra ID authentication beginning on
this date. Existing OAuth2 connections will continue to work until November 15, 2025, and they
should be switched to use Entra ID authentication to avoid disruptions.

Why is this needed?

This change is a result of the Yammer REST API deprecating support for OAuth 2.0

Impact
This deprecation impacts all existing Viva Engage connector implementations currently utilizing
OAuth 2.0 connections.

Replacement feature
All implementations utilizing the Viva Engage connector must migrate to using Entra ID
connections, and all new implementations need to utilize Entra ID connections.

Deprecation of support for the contact tracking

feature in Dynamics 365 App for Outlook
Starting October 1, 2025, the contact tracking feature in Dynamics 365 App for Outlook will
reach end of support. This feature allowed users to track Outlook contacts directly in Dynamics
365 Sales from the Outlook (classic) desktop application.

Why is this needed?

This change aligns with the evolution of Outlook, as the contact tracking functionality isn't
available in the new Outlook experience. Microsoft is focusing on supporting features that are
compatible with the latest Outlook versions and providing a consistent experience across
platforms.

Impact
This deprecation only impacts users of the Outlook (classic) desktop application who use the
contact tracking feature. Users of the new Outlook aren't affected.

Replacement feature
There's no direct replacement for the contact tracking feature in the new Outlook. As an
alternative, users can manually add contacts to Dynamics 365 Sales using the application.

Deprecation of support for personal Microsoft

service accounts in Power Automate
Starting May 27, 2025, support for personal Microsoft service accounts will be deprecated in
Power Automate. This deprecation will end July 26, 2025. To continue using Power Automate,
users must perform the procedure in the Replacement feature section before deprecation ends.

Power Automate for desktop won't be affected and will continue to work with personal email
accounts.

Why is this needed?

The deprecation of personal accounts in Power Automate is aimed at enhancing security and
aligning the platform with professional, enterprise-grade standards. Work or school accounts
offer the robust authentication, enterprise-level security, and advanced functionality needed to
ensure a seamless and secure experience for managing automation workflows in modern
environments. This transition reflects a commitment to delivering a more reliable and focused
tool for professional use.

Impact
After deprecation ends, Microsoft service account users will experience the following changes:

Users can't log into the Power Automate portal or mobile app with personal email
accounts, such as [Link] or [Link].
Users can't create, edit, or manage cloud flows on the portal or mobile app.
Access to any cloud flows associated with Microsoft service accounts are permanently
removed, and these cloud flows are deleted.

Replacement feature
To continue using Power Automate, we recommend that you transition to the Power Apps
Developer Plan. This transition provides access to modern features and allows for seamless
management of your workflows. The Power Apps Developer Plan includes flow creation and
integration with Microsoft Dataverse, making it an excellent option for automation enthusiasts
and professionals.

1. If you don't have a trial Azure account , create one.

2. Using the Azure account you created, set up a new Microsoft Entra tenant.

3. Using the Azure account and Entra tenant you set up in this procedure, create a Power
Apps developer environment.

Learn more about capabilities in About the Developer Plan.

4. Export your cloud flows created using your Microsoft account.

5. Import the cloud flows you exported in the previous step into the newly created Power
Apps developer environment.

Deprecation of SQL server connector's V1 actions

The SQL server connector's V1 actions are being retired and starting 30 June 2025 these
actions will no longer be supported and will be disabled.

We have V2 actions already available in the SQL server connector that can be used as an
alternative. You can find more details about the new V2 actions here: SQL server actions. We
strongly encourage you to migrate to the new V2 actions as soon as possible to take full
advantage of these improvements.

How does this affect me?

If action isn't taken, beginning 30 June 2025, the applications using the V1 actions of SQL
server will be impacted and might no longer function as expected.

Required action
Be sure to replace the V1 actions with the new V2 actions of the SQL server connector in all of
the applications utilizing it. If you need assistance in Migrating V1 operations to V2 equivalent.
Check here: SQL server actions

Deprecation of rich text editor classic experience

Starting April 18, 2025, the classic rich text editor experience will be deprecated and no longer
supported in Dynamics 365 apps. The new, modernized rich text editor is the default
experience, and customers who use the classic experience will be upgraded automatically.
Learn more in Modern text editor enhancements.

Deprecation of Cards for Power Apps

Effective August 29, 2025, Cards for Power Apps will be deprecated and no longer supported.
As a result, any Cards for Power Apps that have been built and shared in Microsoft Teams won't
function. Users won't be able to create new cards or execute existing ones.

We recommend migrating any functionality you rely on from Cards for Power Apps before the
deprecation date. Consider transitioning to either Adaptive Cards in Copilot Studio or adaptive
cards for Microsoft Teams for similar functionality.

Deprecation of Train with examples to transform

examples to Power Fx formulas
Effective February 19, 2025, the Train with examples feature to transform examples to Power Fx
formulas is deprecated and no longer supported. We recommend using Transform natural
language to Power Fx formulas.

Deprecation of Snowflake connector [Deprecated]

The Snowflake connector was discontinued on May 26, 2025. A new and improved version with
more features is now available. For more details, go to the new Snowflake (Preview) connector
reference article. We encourage you to switch soon to take advantage of the upgrades.
What action do I need to take?
Make sure you replace your existing connections of the deprecated Snowflake connector with
the new Snowflake (Preview) connector in all of the applications utilizing this connector. If you
need assistance in replacing your connections in Power Automate Flows or Power Apps, refer
to the below following documentation:

Manage connections in Power Automate - Power Automate | Microsoft Learn

Manage connections in canvas apps - Power Apps | Microsoft Learn

Impact
If action isn't taken by May 26, 2025, the applications utilizing the Snowflake (Deprecated)
connector will no longer function as expected.

Deprecation of Ask a virtual agent

Effective March 11, 2025, the Ask a virtual agent feature in Power Apps is deprecated and no
longer supported. We recommend using Copilot in Power Apps for assistance when creating an
app. For general help in Power Apps, select Help (question mark icon in the upper right) >
Support > Problem.

Deprecation of bring-your-own-key (BYOK)

Dataverse service
Starting January 6, 2026, we'll discontinue support for the bring-your-own-key (BYOK) feature.
Customers are encouraged to transition to customer-managed keys (CMK), an enhanced
solution that offers improved functionality, broader support for data sources, and better
performance.

What happens if migration isn't completed?

Effective June 1, 2025, customers will be unable to apply BYOK to production environments.

If your migration to CMK isn't completed by January 6, 2026, your environment will
automatically revert to Microsoft-managed keys. While this ensures continuity of encryption, it
limits the control and flexibility you currently enjoy with BYOK. To avoid disruption and take full
advantage of the enhanced features and security offered by CMK, we strongly recommend
beginning your migration process as soon as possible.
We recommend starting your transition to CMK (customer-managed keys) at your earliest
convenience. For more information, go to Manage your customer-managed encryption key
and Migrate bring-your-own-key (BYOK) environments to customer-managed key.

Deprecation of Organization Insights Dashboard

The Organization Insights dashboard has been deprecated from the Microsoft Power Apps
Default Solution dashboards. Similar organization insights are available in Microsoft Dataverse
analytics.

As part of a service update to enhance security in Power Apps, we're removing Highcharts
version 4.2.3.

Deprecation of support for multitenant apps

without a service principal in the Microsoft Entra
ID tenant
To boost security and system performance, we're updating authentication protocols for
multitenant apps in the Dataverse platform. Starting October 2024, app-only tokens for apps
without a service principal in the target tenant aren't supported. This change is essential for
mitigating vulnerabilities and safeguarding your data from potential threats.

Why is this needed?

Multitenant apps that don't have a client service principal have been recognized as vulnerable.
They pose a significant risk of acquiring cross-tenant, open authorization (OAuth) app-only
tokens for multitenant services across arbitrary tenants. To address this security vulnerability,
apps without a service principal in the tenant are no longer authenticated. Dataverse APIs fail
from these apps in deprecated environments.

Impact
Token generation for multitenant apps fail if the service principal for that app isn't present in
the target tenant.

Action required by you

To ensure the security and integrity of your system and data, we encourage customers to
provision the multitenant apps in their Microsoft Entra ID tenant. Learn more in Create an
enterprise application from a multitenant application.

７ Note

If application onboarding isn't expected, remove that app or replace it with a compliant
app that has a client service principal in the tenant.

Make sure that the access token being acquired is from your tenant endpoint
( [Link] ), not your organization endpoint
( [Link] ).

When is this change coming into effect?

Support for app-only tokens by multitenant apps that don't have a service principal ID in the
Target Tenant will be removed by October 2024.

Deprecation of hierarchy control in model-driven

apps
Effective October 2024, the hierarchy control, which is used to define and query hierarchically
related data in model-driven apps, is deprecated. The control continues to work in existing
apps until October 2025, at which time it will be removed from the product.

The hierarchy control allows users to visualize relationships between records for a table. This is
applicable for any table that has a self-referential relationship.

Why is this needed?

Due to low usage, issues with accessibility, and incompatibility with the modern look, the
hierarchy control will no longer be supported.

Impact
After its removal, end users won't be able to view the visual representation of the hierarchical
relationships of records.

Action required by you

You can temporarily enable the control until its removed in the product by editing the app
settings. Go to Power Apps ([Link]) and open the app you want for editing.
Then go to Settings > Features tab and enable the Enable the "View hierarchy" capability
setting.

This feature is fully removed October 2025.

If a hierarchy view is essential to your app, you have a couple options:

Dynamics 365 Sales customers can use the new hierarchy visualization feature. This
customizable control supports in place editing, with the ability to define complex multi-
table hierarchies. More information: Overview of hierarchy visualization
Customers with more technical expertise can build and deploy their own custom PCF
control. For information about how to create a code component, go to Create and build a
code component.

Deprecation of schema for data policy activity

logging
The schema for data policy activity logging is deprecated and won't be available starting in July
2024. You can use the new schema available at Activity category: Data policy events.

Deprecation of schema for Lockbox audit events

The schema for Lockbox audit events is deprecated and won't be available starting in July 2024.
You can audit Customer Lockbox events using the new schema available at Activity category:
Lockbox operations.

ISV Studio removed

ISV Studio was a preview analytics portal that showed limited install data for ISV solutions built
on Dynamics CE or Power Platform and deployed from AppSource. It also provided another
access point to the connector certification wizard.

Thanks to our ISV partners for trying out ISV Studio during the preview. After careful
consideration and extensive review of partner feedback, we recognized the limitations of the
service over time and acknowledged that it didn't provide the expected value. ISV Studio was
deprecated on April 1, 2024 and removed on May 31, 2024.

To continue accessing analytics related to your AppSource solutions, use the reporting features
in Partner Center. Although this alternative might not offer the same data from ISV Studio,
Partner Center serves as a valuable resource for insights and tools to empower your business
growth and success.

Connector Certification Portal Deprecation

The Connector Certification Portal was a preview portal that allowed partners to submit and
certify connectors created using the Power Query SDK. Once certified, these connectors would
ship in products such as Power BI Desktop, On-Premises Data Gateway and Power Query
Online in general.

After careful consideration, and thanks to the feedback from partners, a decision was made to
decommission the portal starting January 15, 2025.

While the portal will be decommissioned, the program continues. For the latest information on
the status of the program and how to certify your connector, learn more about the Data
Factory Connector Certification.

Data policy resource exemption feature

Effective March 2024, the data policy resource exemption feature is deprecated for tenants that
never used it. By October 2024, the resource exemption feature will be deprecated for all
customers.

Activity Editor was removed in model-driven apps

As part of a service update designed to improve security within Power Apps, we removed the
deprecated Activity Editor control, and recommend the use of the rich text editor control. This
change rolled out in January and February 2024.

Learn more about adding the rich text editor control to a model-driven app. If you're using the
Activity Editor control in a customized email or appointment experience in a model-driven app,
learn more about switching to the rich text editor control.

Classic app, form, and view designers are

deprecated
Starting in October 2023, the classic app, form, and view designers are deprecated, by default.
This means that, by default, all model-driven apps, forms, and views only open via the modern
designers. By default, the Switch to classic option to revert back to the classic designers from
the modern designers is no longer available.
Impact
Depending on your geographic location and rollout cadence, this change impacts you in mid-
October 2023. Makers have to reach out to their admin to access the classic designers.

Re-enabling the classic designers

Admins can turn the Switch to classic option back on in the Power Platform admin center for
specific environments. The modern app, form, and view designers are at core feature parity
with the deprecated classic designers. As such, makers are expected to fully transition to use
only the modern designers to build model-driven apps and components. More information:
Manage behavior settings

Dynamics 365 for phones and tablets is deprecated

for online users and replaced by Power Apps
Effective April 2024, Dynamics 365 for phones and tablets (iOS and Android) are deprecated for
online users. Online users must migrate to the Power Apps mobile app. The Power Apps mobile
app provides updated capabilities, a modern user experience, and fast load times.

Deprecation of support of unregistered MSA and

External Microsoft Entra users in Dataverse
As part of our ongoing efforts to enhance the security and performance of Dataverse platform,
we're announcing deprecation of support to unregistered MSA and externals Microsoft Entra
users in Dataverse due to its relative obscurity and complexity associated with this feature in
authorization scenario.

What's changing?
If Microsoft Accounts (MSA) or Microsoft Entra accounts aren't registered in your Microsoft
Entra tenant, you can't access Dataverse on the common endpoint.

You might see an error message similar to this one:

Microsoft EntraSTS50020: user account <contoso@[Link]> ; from identity provider

[Link] ID}/ doesn't exist in tenant '{tenant name}' and can't access

the application '{application ID}'(Dataverse org name) in that tenant.

The account must be added as an external user in the tenant. Sign out and sign in again with a
different Microsoft Entra user account. Previously, Dataverse denied access to these accounts,
but now they're blocked at the Microsoft Entra tenant level. This change doesn't affect GDAP or
CSP users.

What do you need to do?

If a user who isn't part of your Microsoft Entra ID needs access to a Dataverse organization, the
user needs to be added to the tenant as an external user or guest user. Learn more in Add B2B
collaboration users in the Microsoft Entra admin center. Additionally, you can restrict access to
the Dataverse organization by reviewing the access granted to external users by following the
steps below.

Disable sharing apps with everyone: You can assess if sharing applications with everyone
(including guests) is a requirement for cross-team collaboration. If it isn't, then you can disable
sharing with everyone using the following PowerShell script:

PowerShell
$tenantSettings = Get-TenantSettings
$[Link] = $true
Set-TenantSettings $tenantSettings

Disable guests from making apps: You can review if guests making apps in your organization
are required. You can disable it if guests aren't expected to be makers (such as, customizing
SharePoint forms). This option already defaults to $false .

PowerShell
$tenantSettings = Get-TenantSettings
$[Link] = $false
Set-TenantSettings $tenantSettings

When is this change coming into effect?

We removed support of unregistered MSA and external Microsoft Entra users in the Dataverse
in October 2023.

jQuery 2.1.1 was removed in model-driven apps

As part of a service update designed to improve security within Microsoft Power Apps, we
removed jQuery version 2.1.1 from model-driven applications. One year after announcing the
plan to remove this library, in October 2023 we removed the library located here:
/_static/_common/scripts/[Link] .

If custom code in web resources had a dependency on this library, it stopped working when
this library was removed. This was unsupported pattern as use of any model-driven application
client-side code isn't supported, including libraries that model-driven apps depend on. These
libraries might change without warning. More information: Unsupported customizations.

Are you impacted?

Now that the library is removed, you see errors in any web resources that depended on this
library. You can search your web resource code for this line: /_static/_common/scripts/jquery-
[Link] .

If your code isn't already in a source code repository, you should export your solutions and
extract the contents. There are many tools you might use to search the contents. For example,
you can use the search capabilities of Visual Studio Code. More information: Visual Studio
Code: Basic Editing > Search across files

What to do if you're impacted?

If your web resources had a dependency on this library, you should replace the reference with
a newer version of JQuery.

Note, there might be breaking changes between versions. For information about upgrading,
see jQuery Core Upgrade Guides .

Choose one of these options:

Create a new JavaScript web resource with the minified version of jQuery. The library is
available here: jQuery Core – All Versions . More information: Create or edit model-
driven app web resources to extend an app.
Locate the URL of a CDN for a newer version of jQuery. For example: jQuery-libraries-
cdnjs .

Replace the reference to /_static/_common/scripts/[Link] with the name of the

web resource you created or the URL to the CDN resource with a newer version of jQuery.

AI Builder image classification model by Lobe is

deprecated
Effective January 2023, the image classification model by Lobe (preview) was deprecated.

The model allowed you to quickly create and train models to classify images into different
categories. This was useful for classifying objects in images, such as animals, plants, and
vehicles. The deprecation of this capability was needed because the model wasn't aligned with
other models in AI Builder, which offer an in-browser training and model usage experience.
These other models don't require a download and install.

The impact of the deprecation of this capability is that you'll no longer be able to use the
model to classify images and you won't be able to download the Lobe application. Models
built with Lobe might continue to work and serve their purpose, but they won't be supported
by the AI Builder team. Your Lobe installation might also continue to function, but won't be
supported.

If you're impacted by the deprecation of this feature, you can use other methods to classify
images, such as Azure Cognitive Services for Custom Vision. Custom Vision is a cloud-based
image classification service that enables you to quickly and easily create custom image
classifiers. With Custom Vision, you can upload your own images and label them with the
categories you want the model to recognize. The service then uses machine learning to train a
custom model that can accurately identify the categories in new images. The service also
provides a range of tools to evaluate and improve your models, such as testing accuracy and
providing feedback on how to improve the model. You can also create custom image classifiers
that can be used for various applications, such as object recognition, facial recognition, and
more.

Model-driven app controls deprecation

Effective January 2023, the following controls for model-driven apps are deprecated:
autocomplete, input mask, multimedia player, number input, and star rating.

Why is this needed?

We are introducing new Fluent UI controls that have better usability, accessibility, and dark
mode support.

Impact
Starting April 2023, these controls can no longer be added to forms.
No more support or fixes will be provided on these controls after April 2024.

Action required by you

Evaluate existing forms that include a deprecated control and replace them with a newer
control.

Microsoft Dataverse (legacy) connector for Power

Automate flows is deprecated
Effective October 2022, the Microsoft Dataverse (legacy) connector (previously referred to as
the CDS 2.0 connector) is deprecated. The connector continues to work in existing flows until a
final date is announced. You have one year from the date of announcement to move to the
Microsoft Dataverse connector.

Why is this needed?

The Microsoft Dataverse connector has replaced the Microsoft Dataverse (legacy) as the main
connector for automating data, events, and actions in Microsoft Dataverse. It provides more
actions, triggers, and improvements to working with Dataverse, including better reliability and
faster performance when used in the same Power Platform environment.

Impact
Cloud flows that use the Microsoft Dataverse (legacy) connector need to be updated to use the
Microsoft Dataverse connector instead.

Action required by you

Review the cloud flows you own that use the Microsoft Dataverse (legacy) connector and
identify which are ready to update. As of January 2024, most flows using the legacy connector
are recommended for migration except for flows triggering based on changes in other
environments.

A migration assistant is available on the detail page of cloud flows that are able to be
automatically updated. The assistant creates a copy of the flow with the legacy connector's
triggers, actions, and dynamic content references replaced.

Microsoft Dataverse (legacy) connector for Azure

Logic Apps will be deprecated and replaced with
another connector
Effective October 2022, the Microsoft Dataverse (legacy) connector (also referred to as the CDS
2.0 connector) was deprecated. This connector was used to connect to Dataverse for use in
multiple clients and components. The Microsoft Dataverse connector was made available for
use in Azure Logic Apps starting August 2022. The Dataverse connector provides both legacy
triggers and actions and new preview triggers and actions for the newest connector. Dates for
when previews will be generally available will be provided by November 2023.

There will be a phased-in approach before deprecation takes place. Here's the timeline:

August 30, 2022: The actions and triggers in Dataverse legacy connector became
available in the Dataverse connector.
Existing Dataverse Legacy connector triggers and actions can continue to be used in
existing logic apps for backward compatibility for time with more timelines available in
August 2023.
All new logic apps are created using the new actions.
August 2022 through preview period: Both new and legacy actions and triggers are
available during new flow creation. By January 2024, a date for the move to general
availability will be provided.
Date TBD: No new logic apps can be created using the legacy actions and triggers, but
existing logic apps with those actions and triggers will continue to work. Updates will be
provided in January 2024.

In August 2023, we provided a timeline when all existing logic apps using the deprecated
legacy actions and triggers will stop working. Users need to review their existing logic apps to
update them to the new Azure Logic Apps triggers by the specified timeline (typically one year
from the announcement date).

Internet Explorer 11 support for Dynamics 365 and

Microsoft Power Platform is deprecated
Dynamics 365 and Microsoft Power Platform will be blocked in Internet Explorer starting
October 31. From early October 2022, users will be redirected to Microsoft Edge if they have
Microsoft Edge currently installed on their device. Otherwise, they'll receive a nondismissible
message informing them why they're blocked and to try using the site on Microsoft Edge.
Starting October 31, Internet Explorer will be blocked on Dynamics 365 and Microsoft Power
Platform and users will see a blocking message informing them to use Microsoft Edge. If users
are trying to access Dynamics 365 and Microsoft Power Platform on a Microsoft Edge version
that is no longer supported, they'll be prompted to use the latest version of Microsoft Edge.

We recommend that customers transition to Microsoft Edge .

We recommend Dynamics 365 App for Outlook users that are using the Outlook desktop client
upgrade their clients to Microsoft Outlook versions that use Microsoft Edge WebView2 or
Microsoft Outlook on the web (OWA).

More information: Support end for Internet Explorer.

If you have more questions, contact your Microsoft Customer Service representative or
Microsoft Partner.

The legacy read-only grid in model-driven apps is

deprecated
The legacy read-only grid control has been deprecated in model-driven apps with the 2022
release wave 1. This control is being replaced by the Power Apps read-only grid, which
became the default read-only grid experience for all environments for model-driven apps with
the 2022 release wave 1.

Why is this needed?

The legacy read-only grid:

Doesn't support the latest Microsoft accessibility standards.

Doesn't align with the latest in Microsoft design guidance.
Has limited extensibility options.

Impact
Tables configured to use the Read-only Grid (Default) control are replaced with the Power Apps
read-only grid for views and subgrids. This change started with the 2022 release wave 1.

When the Power Apps read-only grid is originally enabled, the jump bar row isn't visible;
however, makers can re-enable this as needed. More information: Configure the Power Apps
read-only grid control

Dynamics 365 (Preview) app for Windows is

deprecated
The Microsoft Dynamics 365 (Preview) app for Windows was deprecated on June 20, 2022. The
app is no longer supported.
You can still run your Dynamics 365 apps on Powers Apps for Windows with the same set of
features and capabilities. For more information, see Install Powers Apps for Windows.

Admin mode custom message deprecated

Effective July 1, 2022, the Custom message field is deprecated from the environment Edit
details page.

Power Apps for Windows 8 will be deprecated and

replaced with a new app
Effective September 2022, Power Apps for Windows 8 will be deprecated. Microsoft will
continue to provide security and other critical updates for the app until Sept 20, 2022. We
won't release any other features or functionalities for the app.

After Sept 20, 2022, Power Apps for Windows 8 will be removed from the Microsoft Store, and
will no longer be supported.

On June 20, 2022 Power Apps for Windows will be available. For more information about the
new app, see Install Powers Apps for Windows.

Data Export Service deprecation

Effective November 2021, Data Export Service was deprecated. Data Export Service will
continue to work and will be fully supported until it reaches end-of-support and end-of-life in
November 2022. This will impact Dynamics 365 and Power Platform customers who use Data
Export Service add-on from Microsoft AppSource. The Data Export Service add-on won't be
available for download for all customers. We recommend that customers transition to Azure
Synapse Link for Dataverse. For more information, see our blog or download the deprecation
playbook .

Dataverse OData v2.0 Service removal

We plan to remove the Organization Data Service. Any code that uses the Organization Data
Service should be migrated to use the Web API before that time.

The original removal date was November 11, 2022, but this was extended to April 30, 2023. We
have decided not to remove the service on April 30, 2023.
We're going to defer the removal of this service to allow people more time to complete the
transition of their code to use the Web API. If you have detected that you're still using this
endpoint, you must prioritize transitioning this code to use Web API so you'll be prepared
when the final removal date is announced.

７ Note

This announcement doesn't involve the deprecated SDK for .NET SOAP endpoint. At this
time, no date has been announced for the removal of the SOAP endpoint.

The Organization Data Service is an OData v2.0 endpoint introduced with Dynamics CRM 2011.
The Organization Data Service was deprecated with Dynamics 365 Customer Engagement v8.0
in favor of the Web API, an OData v4.0 service. Today, less than .06% of requests to Dataverse
use this endpoint. Removing this endpoint will enable Dataverse to improve overall
performance.

More information: OData v2.0 Service removal date announcement .

Support for Microsoft 365 Groups and Yammer in

Dynamics 365 is deprecated
Effective February 2022, support for Microsoft 365 Groups (previously known as Office Groups)
and Yammer in Dynamics 365 will be deprecated. This will impact customers who use Microsoft
365 Groups and/or Yammer for collaboration in Dynamics 365. We recommend that customers
transition to Microsoft Teams for more advanced collaboration functionalities. For information
about integrating Dynamics 365 with Teams, see Integrate customer engagement apps in
Dynamics 365 with Microsoft Teams.

Existing customers can create teams from their existing Microsoft 365 Groups and map them to
individual records as per the requirements. They can also continue to use Microsoft 365 Groups
but have a custom experience to host it inside Dynamics 365.

If you have questions about the deprecation, contact your Microsoft Customer Service
representative or Microsoft Partner.

Support for viewing and managing application

users in legacy web client is deprecated
Effective February 2022, the list of "Application Users" won't be available under Advanced
Settings > Security > Users. You can use the Power Platform admin center to view and manage
application users. See Manage application users in the Power Platform admin center.

The Analyze section, in mobile offline profiles is

deprecated
Effective September 2021, the Analyze action and the Offline profile report that is used to
configure mobile offline profiles is deprecated. The Analyze feature is being removed because
of Cross-Site Scripts (XSS) vulnerabilities. The report is used to identify components that aren't
available when you're working in offline mode. The capabilities will be reimagined as part of
the ongoing enhancements of the mobile offline configuration experience. There's no action
required by you.

Dynamics 365 - Gamification is deprecated

Effective April 1, 2021, Dynamics 365 – Gamification is deprecated. Until September 30, 2021,
Microsoft provided limited support for this solution. From October 1, 2021, the Dynamics 365 –
Gamification solution won't be functional. To uninstall Gamification, delete the
GamificationUpdater and Gamification solutions from the Dynamics 365 organization. Note
that you must first delete the GamificationUpdater solution followed by the Gamification
solution. More information: Delete a preferred solution.

Skype integration with customer engagement apps

is deprecated
Effective July 2019, Skype integration feature with customer engagement apps has been
deprecated and is no longer supported after July 31, 2021. Skype is retired on July 31, 2021;
more information: Skype for Business Online retirement - Microsoft Teams

The presence indication backed by Skype for Business will no longer function. This deprecation
includes presence indication in hover cards, lookup fields, and lookup columns in grids. There
are currently plans to support these locations via Teams. In the meantime, presence indication
can be found in Live Person Cards.

Plan to transition to Microsoft Teams, because the Team's capabilities go beyond those of
Skype for Business Online. Teams is the next chapter in enterprise communication solution
from Microsoft.
Low-density headers in model-driven apps won't
be supported with the 2021 release wave 2
With the upcoming 2021 release wave 2 (public preview in August 2021 and GA in October
2021), the low-density header option, and runtime experience won't be supported in model-
driven app forms.

Why is this needed?

Makers have moved away from low-density headers and usage is low.
Low-density headers don't promote a highly dense experience and require users to
always use the flyout for all controls across view-port sizes from small to very-wide.

Impact
Any current form that is configured to be "low-density" is automatically updated to render in a
high density with flyout mode in a model driven app. Below is an example of high-density
header with flyout:

Action required by you

To meet the October 2021 deadline, be sure you update any of your forms from a low-density
format to a high density with flyout mode using the modern form designer. More information:
Configure header density.

If you don't make this change, the form no longer honors this setting at runtime. It also
defaults to high density with flyout.

Form footers in model-driven apps won't be

supported with the 2021 release wave 2
With the upcoming 2021 release wave 2 (public preview in August 2021 and GA in October
2021), form footers won't be supported in a model-driven app form.

Why is this needed?

The footer doesn't meet the Microsoft Web Content Accessibility Guidelines (WCAG) 2.0
compliance for accessibility.
Data density is highly impacted by the form footer and doesn't support a good customer
experience. Controls aren't discoverable and lead to many customer usability issues.
Makers have moved away from adding controls into the footer and there's low usage of
other controls, out of box or custom, in the current form footer experiences.
Components created using Power Apps component framework aren't fully compatible
with form footers, which cause usability issues when added to a form footer.
Form footers aren't included in the mobile experience or on the view and dashboard
pages. This change will align the form experience with other pages in a model-driven app.

Impact
Main forms will no longer include the footer when a record is opened. Any out of box or
custom controls that have been added to the form footer will no longer be available and you'll
need to remove the fields if they're no longer necessary or move the fields to the header and
use the high-density header with flyout or add them onto the main form. The recommended
approach is to move fields that users need to access regardless of the form tab a user is on to
the header and set it to use the high-density header with flyout. If there's only one tab, the
recommendation is to move them into a new section on the form.

Action required by you

To meet the October 2021 deadline, be sure you move fields or controls added to a form
footer to either the header or a section on the form.
If you do nothing, the footer fields or controls that you've added no longer render on the
form and aren't available to users.

The out of box fields currently on the footer is removed and included on the form as part of
the 2021 release wave 2 updates. So, you don't lose status, unsaved changes, or the option to
open a form in a new window. The Save option is already available in the command bar and is
always visible to the user.

While we understand that these types of changes can be disruptive for makers that use the
footer today, we always evaluate the experiences. We do this to ensure they provide a modern
experience that improves usability, support accessibility requirements, and improves
discoverability for highly used fields and controls on a page.

Model-driven app controls deprecation (2021

Release Wave 1)
With the upcoming 2021 release wave 1 (public preview in February 2021 and GA in April
2021), some older controls for model-driven apps will be deprecated. These controls include
Flip Switch, Calendar Control (V1), Linear Slider, Radial Knob, Arc Knob, Linear Gauge; along
with the Website Preview control, MultiSelectPicklistControl (V1), and the Flip Label (two radio
buttons format option).

Why is this needed?

These controls are outdated and don't conform to our current standards for useability
and accessibility.
For example, we've received feedback that the Flip Label control is difficult to determine
its intended use and users commonly don't see the options available to choose from,
such as "yes / no" or "enable / disable."

Impact
Starting April 2021, these controls can no longer be added to forms.
For instances of Flip Label control, the control will be replaced with a dropdown control.
For all other controls, they'll continue to work within existing forms until April 2022.

Action required by you

We won't make other changes to forms or controls. Makers are encouraged to make updates:

Use the Toggle control as a replacement for Flip Label and Flip Switch.
Use the Calendar Control (V2) as a replacement for Calendar Control (V1).
Evaluate other deprecated controls to determine if they're still useful within existing
forms.

Microsoft Dynamics 365 Email Router is

deprecated
The Email Router was deprecated on July 17, 2018 and it will no longer function starting April
12, 2021. Although the Email Router might still have worked with Dynamics 365 on-premises,
this configuration is no longer supported. All email routing functionality should be migrated to
use server-side synchronization. For information on migrating email routing functionality to
use the server-side synchronization feature, see: Migrate settings from the Email Router to
server-side synchronization.

The Microsoft Dynamics 365 application for

Windows is deprecated
Effective April 2021, the Microsoft Dynamics 365 app for Windows that lets you run customer
engagement apps (such as Dynamics 365 Sales, Dynamics 365 Customer Service, and Dynamics
365 Marketing) has been deprecated.

Microsoft continues to provide security and other critical updates for the Microsoft Dynamics
365 app for Windows until January 29, 2021. We won't release any other features or
functionalities for the app. After April 1, 2021, the app is removed from the Microsoft Store,
and is no longer supported.

We recommend that you start using your web browser as soon as possible to run your
customer engagement apps, such as Dynamics 365 Sales, Dynamics 365 Customer Service, and
Dynamics 365 Marketing. Run them on Windows to take advantage of the ongoing
improvements for the web app.

Organization data download filters for mobile

offline are deprecated
Effective February 2021, Organization data download filter option that filters the data when
you set up mobile offline are deprecated. We recommend that you start preparing your
organization and move relevant data filters from Organization data download filter to the
offline profile option, which lets you determine what data is available when users work in
offline mode. For more information, see Create a mobile offline synchronization. Once the old
filter criteria have been moved to offline profile, you can clear or delete the filters set in
Organization data download filter.

TLS RSA cipher suites are deprecated

Effective October 30, 2020, the following cipher suites are being deprecated from our servers.

"TLS_RSA_WITH_AES_256_GCM_SHA384"
 "TLS_RSA_WITH_AES_128_GCM_SHA256"
"TLS_RSA_WITH_AES_256_CBC_SHA256"
"TLS_RSA_WITH_AES_128_CBC_SHA256"

Cipher suites are used to encrypt messages to secure a network connection between
clients/servers and other servers. We're removing the above list of cipher suites to comply with
our current security protocols.

Beginning March 1, 2021, customers can only use our standard cipher suites. This change
impacts your clients and servers that communicate with our servers, for example, syncing
emails from your Microsoft Exchange server, running outbound plug-ins, using native (local)
clients to access our servers.

Customers must upgrade their servers before March 1, 2021. For more information about
configuring TLS Cipher Suite order, see Manage Transport Layer Security (TLS).

Document suggestions for all entities except case

are deprecated
Effective October 20, 2020, the document suggestions feature has been deprecated for all
entities, except the case entity. The case entity is available with Dynamics 365 Customer
Service. More information: Enable document suggestions to recommend related documents

Automatic record creation rules and SLA items in

web client are deprecated
Effective October 1, 2020, the automatic record creation and update rules and service-level
agreements (SLAs) have been deprecated in the web client. For more information, go to
Deprecations in Customer Service.

TimeZoneRule entity and some attributes of

TimeZoneDefinition entity are deprecated
Effective September 24, 2020, the TimeZoneRule entity and the Bias and RetiredOrder
attributes of the TimeZoneDefinition entity are deprecated and will be removed in a future
release. For all client-side time zone calculations, use the LocalTimeFromUtcTime and
UtcTimeFromLocalTime functions in Web API or the TimeZoneInfo class in the .NET SDK. More

information: Blog: Deprecation of time zone entities in Microsoft Dataverse

Online management API PowerShell module and
REST API are deprecated
Effective August 26, 2020, the online management API PowerShell module, and the underlying
[Online Management REST API] are deprecated. The online management API PowerShell
module will be updated in October 2020 to point to newer underlying APIs and won't receive
further updates. We recommend that you use the Power Apps administration module. More
information: Get started using the Power Apps admin module

Company News Timeline solution is deprecated

Effective July 10, 2020, the Company News Timeline solution, is deprecated. Until September
10, 2020, Microsoft will continue to provide support for the feature, but won't release any other
functionality beyond what is already present. Starting September 10, 2020, you'll need to
uninstall the solution, which will remove the news widget from the Account record pages.

1. To remove the solution, go to Advanced settings and select Solutions.

2. Select CompanyNewsTimeline and then select Delete.

As an alternative you can install news Power Apps component framework control. For more
information, see Set up and use the news control.

Dynamic 365 Sales bot is deprecated

Effective June 2, 2020, the Dynamics 365 Sales bot, a feature that enables users to retrieve sales
information through a bot within Dynamics 365 Sales app for Teams will be deprecated. Until
July 31, 2020, Microsoft will continue to provide support for the feature, but won't release any
more functionality beyond what is already present. After July 31, 2020, you'll no longer be able
to receive responses to conversations. The bot won't be available for new customers; existing
customers may still be able to access the bot from the Chat, however the bot won't respond to
questions.

It is our goal to deliver a powerful bot experience that allows users to retrieve and manage
information. Based on usage data and feedback from our customers, we're working on a
powerful, extensible set of capabilities and features that will allow you to intuitively access and
interact with sales information—among other entities—through a bot interface. We'll keep you
updated on timing for when this will be available.

Dynamics 365 Connector is deprecated

Effective May 5, 2020, the Dynamics 365 connector used for data integrations, flows, Azure
Logic Apps, and canvas apps is officially deprecated. We recommend that you don't create new
connections using this connector.

Impact
As of October 31, 2022, this connector was shut down for Power Automate flows and canvas
apps using the Power Apps player in Windows. All flows and canvas apps must be migrated to
the Microsoft Dataverse or Dataverse Legacy connector per recommended actions below.

As of October 31, 2022, this connector is in the process of shutting down for Logic Apps. You
must migrate all Logic Apps as soon as possible to the Microsoft Dataverse or Dataverse
Legacy connector per recommended actions below.

You can't create new connections for data integrations using the Dynamics 365 connector. For
these components, shut down is in progress. We recommend use of the Dynamics 365
connector be replaced with an option below as soon as possible.

This connector is shut down for new Power Automate flows; all newly created flows must use
the Microsoft Dataverse (legacy) connector (also referred to as the CDS 2.0 connector) or the
Microsoft Dataverse connector.

Canvas apps can no longer use the Power Apps player in Windows. All Canvas apps must
migrate to the new player.

Behaviors that will be observed

Data integrator
Dynamics 365 connector can't be selected for creating a new integration.
Editing an existing integration won't be allowed, if you attempt to edit you'll be required
to choose a different connector.

Power Automate

Dynamics 365 connector can't be added to new or existing flows.

Existing flows will continue to run until the final deprecation date.

Logic Apps
Dynamics 365 connector can't be selected for creating a new Logic App.
 Existing Logic Apps will continue to run but must be migrated as soon as possible.
You'll be able to edit an existing Logic App.

Canvas apps

The Windows Player for canvas apps will no longer be able to be used.

Action required by you

You must replace usage of the Dynamics 365 connector with the Microsoft Dataverse
connector.

Microsoft Dataverse: This is the newest connector and the main connector available for
Dataverse usage. All new features, performance work, and enhancements will be available
on this connector. A

Mapping of common actions

ﾉ Expand table

Action Dynamics 365 Dataverse Legacy Microsoft Dataverse

Create Trigger When a Record is Created When a row is When a row is added,
(deprecated) added modified, or deleted

Update Trigger When a Record is Updated When a row is When a row is added,
(deprecated) modified modified, or deleted

Delete Trigger When a Record is Deleted When a row is When a row is added,
(deprecated) deleted modified, or deleted

Create Action Create a new record Add a new row Add a new row (preview)
(deprecated) (legacy)

Update Action Update a record (deprecated) Update a row Update a row (preview)
(legacy)

Delete Action Delete a record (deprecated) Delete a row Delete a row (preview)
(legacy)

Retrieve Action Get record (deprecated) Get row (legacy) Get a row by ID (preview)

Retrieve Multiple List records (deprecated) List rows (legacy) List rows (preview)
Action

Recommended action by usage

Data integrator
All new integrations should be created with the Microsoft Dataverse (Legacy) connector.
Dynamics 365 connectors should be replaced with the Microsoft Dataverse (legacy)
connector. The Microsoft Dataverse connector isn't yet available.
Data Integrations will need to be recreated in the Data Integrator using the Microsoft
Dataverse (legacy) connector and then completing setup.

Logic Apps

All new Logic Apps should be created with the Microsoft Dataverse connector. This
connector includes legacy actions, and preview actions. Legacy actions are in GA. The
preview action GA date will be announced in January 2024.
Logic Apps using the Dynamics 365 connector are recommended to move to the
Microsoft Dataverse (legacy) connector until the Microsoft Dataverse connector is
available.
Logic Apps will either need to be recreated to use the Microsoft Dataverse connector or
be edited to change the Dynamics 365 connector to the Microsoft Dataverse connector
and then validating all triggers and actions.

Canvas apps

If you're using the Power Apps Player to launch Power Apps in Windows, you'll need to switch
over to Power Apps for Windows.

AI Builder text classification models are deprecated

Effective April 24, 2020, any text classification models created using AI Builder before this date
will be deprecated. Until May 15, 2020, these models will continue to function, and Microsoft
will continue to provide support, however some functionality may be disabled. After May 15,
2020, these models will no longer work.

Beginning April 24, 2020, customers will need to recreate their existing text classification
models with the new model versions. Any models created after this date will automatically use
the new model versions and require no further action.

After April 24, 2020, customers are encouraged to transition to the new model versions as soon
as possible.

Dynamic 365 for Outlook is deprecated

Effective March 2020, the legacy Dynamics 365 for Outlook (also referred to as Outlook COM
add-in) was deprecated, and is no longer available for customer engagement apps (Dynamics
365 Sales, Customer Service, Marketing, and Field Service). Use the modern Dynamics 365 App
for Outlook instead.

Dynamics 365 Customer Engagement (on-premises) users can continue to use the legacy
Dynamics 365 for Outlook. However, we recommend that you transition to the modern
Dynamics 365 App for Outlook at the earliest. For information and steps to make a smooth
transition, download Dynamics 365 for Outlook (COM add-in) Playbook .

Dynamics 365 Home is deprecated

Effective March 2020, the home page for Dynamics 365 applications
( [Link] ) is deprecated and won't be available on or after June 30, 2021.
The Microsoft 365 apps page ([Link] ) will replace it and provide users
with a single page for productivity and business applications.

Dynamics 365 Home users will see notification about the new location and recommendation to
change browser bookmarks starting October 1, 2020. On or after June 30, 2021, users will no
longer be able to navigate to [Link] from the Office 365 applications list
or the Office 365 application launcher. After June 2021, users who navigate to
[Link] will see an error page.

More information: [Link]

Form processing and object detection preview

models in AI Builder are deprecated
Effective March 5, 2020, any form processing and object detection models created using AI
Builder before this date will be deprecated. Until June 8, 2020, these models will continue to
function, and Microsoft will continue to provide support, however some functionality may be
disabled. After June 8, 2020, these models will no longer work.

Beginning March 5, 2020, customers will need to recreate their existing form processing and
object detection models with the new model versions. Any models created after this date will
automatically use the new model versions and require no further action.

After March 5, 2020, customers are encouraged to transition to the new model versions as
soon as possible.

More information:
 Transition to use a new form processing model version
Transition to use a new object detection model version

Old Dataverse environment URL redirector service

is deprecated
When you access your Dataverse environment for the first time or every time after you have
signed out from a prior session, you're directed to Microsoft Entra ID signing in. In the sign-in
page URL, it contains a set of internal values/codes that include a link to the URL redirector
service. Upon successful login, the URL redirector service directs you to your Dataverse
environment.

The old URL redirector service, [Link], was replaced in September

2019 with the new one, [Link] (just an example; the URL will
differ based on your environment region). The old URL redirector service is deprecated, and will
be removed on March 31, 2020.

This change will impact you if you have created a bookmark of the sign-in page before
September 2019 that contained the link to the old URL redirector service. The users impacted
by this change will see a notification starting February 17, 2020, with instructions to resolve the
issue.

Deprecation of Office365 authentication type and

OrganizationServiceProxy class for connecting to
Dataverse
Effective February 4, 2020, the WS-Trust authentication type that is used by custom clients to
connect to Dataverse is deprecated. This change affects applications that utilize
[Link] and
[Link] classes for the authentication type of
"Office365".

We're making this change to remove a security protocol (WS-Trust) that is inherently insecure
by current encryption standards. While Microsoft has worked hard to protect users who choose
to use this authentication type for the convenience of login process, it has become an
increasing source of concern for Microsoft security and identity protection systems. The WS-
Trust security protocol, when used in conjunction with a user account and password,
implements an authentication flow that presents both the user ID and password to the
authenticating resource in 'clear text' form, relying solely on the transport encryption to
provide security for the initial leg of the authentication, until such point as the token service
returns an authentication token to use. Additionally, the WS-Trust protocol doesn't support
modern forms of multifactor authentication and conditional access controls to customer data.

With this change, the intent is to guide developers away from this authentication flow and help
application developers to utilize the capabilities of Microsoft Entra to secure and protect access
to their applications and customers in Dataverse.

To allow for transition of customers and partner applications:

Effective October 2020, the authentication protocol will be retired for all new tenants.
Effective October 2020, the authentication protocol won't be available in all new regions.
Effective April 20211, the authentication protocol will be retired for all new environments
within a tenant.
Effective April 2022, the authentication protocol will be retired for all new and existing
environments within a tenant.

1The retirement of new environments starts April 1, 2021 and rolls out gradually in all regions
within a 6-week window.

More information: Use of Office365 authentication with the WS-Trust security protocol

Regional Discovery Service is deprecated

Effective March 2, 2020, the regional Discovery Service is deprecated. Microsoft will continue to
provide support, security, and other critical updates for the regional Discovery Service, but
won't release any more functionality beyond what has already been announced. After April 21,
2021, the regional Discovery Service will be shut down.

Customers must transition to using the global OData V4 Discovery Service before April 21,
2021 so their applications aren't impacted. More information: Modify your code to use global
Discovery Service.

Legacy web client is deprecated

As of September 2019, the legacy web client is deprecated. Customers must transition to
Unified Interface before December 4, 2020. Microsoft will continue to provide support, security,
and other critical updates to the legacy web client until December 4, 2020 but won't release
any more functionality beyond what has already been announced.

On December 4, 2020, the legacy web client will no longer be available. Organizations should
make the transition to Unified Interface as soon as possible to take advantage of Microsoft's
ongoing investments in reliability, performance, and functionality.
In the coming months, for those that have not already made the transition, we'll be sending
reminders and scheduling updates to transition customers to Unified Interface prior to
December 4, 2020. For more information and steps to make a smooth transition, see:

Unified Interface Community Group including a Blog and Forum

Getting Started Unified Interface Playbook

User Experience and Unified Interface transition whitepaper

Quick Start Guide – add Unified Interface App to existing environment

Quick Start Guide – set an environment to Unified Interface as default

Task flows are deprecated

Task flows are used to create a step-by-step data entry form for common tasks, such as after-
meeting follow-ups.

Task flows are deprecated and will be removed by October 1, 2021. They'll be replaced by the
immersive experience for business process flows that is planned for release. More information:
Business process flow immersive experiences

Process Dialogs are deprecated

You can use a process dialog to create an interactive step-by-step data entry form that requires
user input to start and run to completion. When you start the dialog process, a wizard-like
interface is presented; users make selections or enter data as they progress through each page
of the wizard.

Process dialogs are deprecated and will be removed by December 1, 2020. Suggested
replacement options include Business Process Flows or Canvas Apps. More information:
Replace dialogs with business process flows or canvas apps

Legacy process-related attributes in entities are

deprecated
The legacy process-related attributes (such as StageId, and TraversedPath) on entities enabled
for business process flows are now deprecated. The SetProcess action for business process
flows is also deprecated. Manipulating these legacy process-related attributes for target entity
records doesn't guarantee consistency of the business process flow state, and isn't a supported
scenario. The recommended way is to use the attributes of the business process flow entity.
More information: Create, retrieve, update, and delete business process flow entity records

Some client APIs are deprecated

The following client APIs are deprecated to reorganize the Xrm client API object model to
better align with the need of using the same client scripts without having to change them
based on the context or the client (web client or the new Unified Interface) where they run. You
should plan to use the new client APIs mentioned in the Replacement Client API column
instead of the deprecated ones. The deprecated client APIs will continue to be available and
supported until they're officially removed from a future major release. A public announcement
here in the documentation, on the Dynamics 365 blog, and in many other places will be made at
least six months before removal.

ﾉ Expand table

Deprecated Client API Replacement Client API Comments

[Link] Forms: Use of the [Link] object

[Link] as a static access to the
Commands: Send it as the primary form context is still
PrimaryControl parameter supported to maintain
backward compatibility
with the existing scripts.
Based on the feedback, we
understand that the usage
of [Link] is high, and it
won't be removed as soon
as some other client API
methods listed in this
section. We encourage you
to use the new way of
getting form content where
possible. More information:
Client API form context
Although [Link] is
deprecated,
[Link] will
continue to work if HTML
web resources embedded
in forms as this is the only
way to access the form
context from the HTML
web resource.
Deprecated Client API Replacement Client API Comments

[Link] [Link] Allows access to the global

context without going
through the form context.

[Link]. [Link] The

getQueryStringParameters [Link]
API will make retrieval of
nonentity bound data
consistent across entity
forms, metadata-driven
dialogs, and task-based
flows. The data will be a
combination of custom
values sent using the query
string and what was
specified in the parameters
in the openForm method.

[Link]. globalContext. Moved to:

getTimeZoneOffsetMinutes userSettings. globalContext.
getTimeZoneOffsetMinutes userSettings

[Link]. globalContext. Moved to:

getUserId userSettings. globalContext.
userId userSettings

[Link]. globalContext. Moved to:

getUserLcid userSettings. globalContext.
languageId userSettings

[Link]. globalContext. Moved to:

getUserName userSettings. globalContext.
userName userSettings

[Link]. globalContext. Moved to:

getUserRoles userSettings. globalContext.
securityRoles userSettings

[Link]. globalContext. Moved to:

getIsAutoSaveEnabled [Link] globalContext.
organizationSettings

[Link]. globalContext. Moved to:

getOrgLcid [Link] globalContext.
organizationSettings

[Link]. globalContext. Moved to:

getOrgUniqueName [Link] globalContext.
organizationSettings
Deprecated Client API Replacement Client API Comments

[Link] No change in the method, but use

typename instead of type for lookup
attributes.

[Link] [Link] GridRow is essentially a

form context. This change
unifies the interface of
GridRow with formContext.

[Link] [Link] GridRowData is form data.

This change unifies the
interface of GridRowData
with formContextData.

[Link] [Link] Moved the offline-related

methods under
[Link]

[Link] Use one of the following: Earlier: An HTML web

resource may interact with
a) Use a custom control created using the [Link] or
Power Apps component framework [Link] objects within
instead of HTML web resources. the form by using
[Link] or
b) On forms, use the [Link].
getContentWindow method of the web
resource control. Now: [Link].* will
work if the HTML web
c) If the getContentWindow method resource is loaded in a
doesn't work, you can use [Link] form container. It won't
to get to the Xrm object inside an HTML work for HTML web
web resource. If the HTML web resource resources that are stand
is opened in a new window, then you alone, or referenced from
should use [Link] instead. the site map or any other
places.

addOnKeyPress Use a custom control created using

Power Apps component framework

fireOnKeyPress Use a custom control created using

Power Apps component framework

removeOnKeyPress Use a custom control created using

Power Apps component framework

showAutoComplete Use a custom control created using

Power Apps component framework
Deprecated Client API Replacement Client API Comments

hideAutoComplete Use a custom control created using

Power Apps component framework

alertDialog [Link]. The new signature is

openAlertDialog consistent with other APIs
(openForm) and takes a
new set of parameters for
flexibility.

[Link]. [Link]. The new signature is

confirmDialog openConfirmDialog consistent with other APIs
(openForm) and takes a
new set of parameters for
flexibility.

[Link]. [Link] Moving device-related

getBarcodeValue actions to [Link]

[Link]. [Link] Moving device-related

getCurrentPosition actions to [Link]

[Link]. [Link]. The isActivityType

isActivityType getEntityMetadata method is synchronous so
it was suitable for ribbon
rules. However, the
replacement method,
getEntityMetadata, is
asynchronous, and isn't
suitable for ribbon rules.

[Link]. [Link]. Moving navigation actions

openEntityForm openForm to [Link]

[Link]. [Link]. Moving navigation actions

openQuickCreate openForm to [Link]

[Link]. [Link]. Moving navigation actions

openWebResource openWebResource to [Link]
Note: This API returns VOID
in Unified Interface.

globalContext. globalContext. The replacement method

organizationSettings. organizationSettings. lets you access the display
baseCurrencyId baseCurrency name along with the ID of
transaction currency.

globalContext. globalContext. The replacement method

userSettings. userSettings. lets you access the display
securityRoles roles
 Deprecated Client API Replacement Client API Comments

name along with the ID of

the security roles.

globalContext. globalContext. The replacement method

userSettings. userSettings. lets you access the display
transactionCurrencyId transactionCurrency name along with the ID of
transaction currency.

getData and setData for None Silverlight is no longer

Silverlight web resources supported. These methods
won't be available after
October 2020.

formContext. formContext.
data. data.
[Link] save

getObject getContentWindow

For information about the new client APIs, see Apply business logic using client scripting in
model-driven apps using JavaScript

[Link]
property is deprecated
All entities supported in Unified Interface are now enabled for the interactive experience in the
new Customer Service Hub app. This implies that the
[Link] property, which indicates whether an entity can be
enabled for interactive experience, is no longer relevant. The corresponding setting for this
property in the Customization tool, Enable for interactive experience, is removed, and the
[Link] property will be removed from the future version.

Voice of the Customer is deprecated

The Voice of the Customer solution is used to create and send surveys for collecting feedback.

As of July 1, 2019, the Voice of the Customer solution is deprecated. Users can create and
distribute new surveys and collect responses from live surveys until July 1, 2020.

A new solution, Dynamics 365 Customer Voice, is generally available to capture customer
feedback using surveys. Customers can learn more about Customer Voice here.
Dynamics 365 for Blackberry is deprecated
As of December 3, 2018, Microsoft Dynamics 365 for Blackberry App is deprecated and will be
removed from the iOS App Store on October 31, 2019. The mobile app is currently available on
the iOS App Store and is designed for Dynamics 365 customers that utilize Blackberry Mobile
Application Management. See more details about the Dynamics 365 for Blackberry app here:
Secure your mobile data with Microsoft Dynamics 365 for Good. After October 31, 2019,
Microsoft Intune will be the only supported mobile application management solution for the
Dynamics 365 for phones application.

Microsoft will continue to provide security and other critical updates to the Dynamics 365 for
Blackberry App until October 31, 2019, but won't release any more features or functionalities
within the app. After October 31, 2019, the Dynamics 365 for Blackberry App will be removed
from the App Store, and support will end.

What should you do?

If you're currently using the Dynamics 365 for Blackberry App together with Mobile Application
Management for Blackberry, plan to migrate to Dynamics 365 for phones by October 31, 2019.
We encourage you to migrate as soon as possible to take advantage of Microsoft's ongoing
investments in the reliability, performance, and functionality of the Dynamics 365 mobile app.

Usage of Parature knowledgebase as the

knowledge management solution is deprecated
Usage of Parature knowledgebase as the knowledge management solution is deprecated. This
feature is replaced by Knowledge Management features in Dynamics 365 Customer Service.

The Knowledge Solution setting in the Knowledge Base Management Settings dialog box,
which provides a connection to Parature, will be removed in a future major release.
Project Service Finder app is deprecated
The Project Service Finder App, available for use with Dynamics 365 Project Service
Automation, is deprecated. The legacy application will be supported for associated legacy
Project Service Automation releases in accordance with Microsoft's Modern Lifecycle Policy .
The functionality available through this app will be available in a future release of Dynamics
365 Project Service Automation application.

Relationship Roles are deprecated

Relationship Roles (Settings > Business Management > Relationship Roles) are being
deprecated along with their user interface components. These will be removed in a future
major release. This feature is replaced by Connection Roles. For more information, go to Create
connections to view relationships between records.

Mail Merge is deprecated

In Dynamics CRM 2016 (version 8.0), we introduced server-side document generation using
Word and Excel templates. You can use these templates to provide standardized documents or
customized data analysis for your organization.
Mail merge from previous versions is deprecated. This includes the mail-merge Word add-in
and mail-merge templates (Settings > Templates > Mail Merge Templates).

More information: Create Word and Excel templates

Announcements are deprecated

Announcements (Settings > Administration > Announcements) are deprecated and will be
removed in a future major release.

Ready-to-use business processes available through

Add Ready to Use Business Processes setting are
deprecated
Ready-to-use business processes available through the Add Ready-to-Use Business Processes
setting (Settings > Data Management > Add Ready-to-Use Business Processes) are
deprecated and will be removed in a future major release. You can find ready-to-use business
processes on Microsoft AppSource.

Silverlight (XAP) web resource is deprecated

The Silverlight (XAP) web resource is deprecated on the web client, and isn't supported on
Unified Interface. Instead of Silverlight web resources, you must use custom controls created
using the HTML web resources with HTML5 to create UI components to visualize and interact
with data.

Gateways for desktop flows are deprecated

Gateways for desktop flows are deprecated. Direct connectivity is the preferred option to run
attended and unattended desktop flows on your machine(s). This feature is no longer
supported from June 30, 2023, and for China regions from September 30, 2023. Switch to our
machine-management capabilities. Learn more about switching from gateways to direct
connectivity.

Canvas apps
See Important upcoming changes and deprecations in canvas apps.
Power Pages
See Important changes coming in Power Pages.

Other deprecation articles

Deprecated features in Dynamics 365 Sales
Deprecated features in Dynamics 365 Customer Service
Deprecated features in Dynamics 365 Field Service
Deprecated features in Universal Resource Scheduling
Removed or deprecated features in Finance and Operations apps

Last updated on 11/18/2025

Copilots and generative AI in Power
Platform
Get an overview of where to find documentation and training for Copilots and generative AI in
Power Platform.

Copilot in Power Platform

ｂ GET STARTED

AI Builder

Copilot Studio

Copilot in Power Apps

Copilot in Power Automate

Copilot in Power Pages

Copilot training for Power Platform

ｄ TRAINING

Get started with Copilot for Microsoft Power Platform

Create Power Platform solutions with AI and Copilot

Create apps, copilots, flows, and more with Microsoft Dataverse and Teams

Explore more training available

Copilot development and deployment

｀ DEPLOY

Track, manage, and scale Copilot adoption

Use Copilot to generate deployment notes in pipelines

Extend Microsoft 365 Copilot

Move data across regions for Copilots and generative AI features

Generative language models used in Dynamics 365 and Power Platform

ｉ REFERENCE

Power Platform CLI pac copilot command

Power Platform generative AI guidance

ｐ CONCEPT

Power Platform Well-Architected: Intelligent application workloads

Ｙ ARCHITECTURE

Power Platform and Copilot Studio Architecture Center: Reference architectures and solution ideas

Responsible AI

ｐ CONCEPT

Responsible AI FAQs for Power Platform

FAQ for Copilot data security and privacy

FAQ for optional data sharing for Copilot features

FAQ for using Copilot to generate deployment notes in pipelines

AI models

ｃ HOW-TO GUIDE

Control preview and experimental AI models

Allow external LLMs for generative responses

Related copilot products and resources

ｐ CONCEPT
Copilot availability in Power Platform by geography, language, product, and feature

Microsoft Learn Copilot learning hub

Microsoft Learn AI learning hub

Generative language models used in
Dynamics 365 and Power Platform
Article • 05/07/2025

Dynamics 365 and Power Platform products use advanced generative language models to
enhance their features. Below is a list of the primary models used in the features.

gpt-4o 2024-05-13
gpt-4o-mini 2024-07-18
gpt-4.5 preview-2025-02-27
o1 2024-12-17
o1-preview 2024-09-12
o1-mini 2024-09-12
text-embedding-ada-002
text-embedding-3-large
text-embedding-3-small
gpt-4.1 2025-04-14
gpt-4.1-mini 2025-04-14
gpt-4.1-nano 2025-04-14
o3 2025-04-16
o4-mini 2025-04-16
fine tuned gpt-4o and gpt-4o-mini models
Move data across regions for Copilots and
generative AI features
Copilots and generative AI features aren't available in all regions and languages. In some cases,
even where there's some in region capacity, data may still have to move outside of the region
for availability reasons or because certain features depend on other capacity or Microsoft
services. For this reason and depending on where your environment is hosted and what
features you use, you might need to allow data movement across regions to use Copilots and
generative AI features. This article explains how to do that.

７ Note

Copilots and generative AI features that are generally available are turned on by
default. However, you might need to allow data movement across regions to use all
Copilot and generative AI features.
If you don't allow data movement across regions, that doesn't turn off all Copilots
and generative AI features. Copilots and generative AI features are allowed as
capacity is made available in the region.
Certain generative AI features are powered by Microsoft 365 services and store data
according to Microsoft 365 terms and data residency commitments.

Regions where data is processed for Copilots and

generative AI features
When you allow data movement across regions, your inputs (prompts) and outputs (results)
might move outside of your region to the location where the generative AI feature is hosted.
We don't use your data to train, retrain, or improve Azure OpenAI Service foundation models.
Learn more about product-specific Copilot availability in the Copilot international availability
report .

The following table lists the regions where your Power Platform or Dynamics 365 environment
is hosted and the corresponding regions where the Azure OpenAI service and Bing search
service are hosted.

ﾉ Expand table
 Region where your Power Platform or Region where Azure Region where data is stored
Dynamics 365 environment is hosted OpenAI Service is and processed for Bing Search
hosted

United States In region* United States

Europe** In EU Data Boundary United States

France In EU Data Boundary United States

Germany
Norway
Sweden
Switzerland**

Brazil United States United States

Canada
Japan
Korea
South Africa
United Arab Emirates

Asia In region* or United United States

Singapore States

Australia In region* or United United States

India States

United Kingdom In region* or in EU Data United States

Boundary

Government cloud (GCC, GCC High) In region* United States

*In region means within the geographical region of your Power Platform or Dynamics 365
environment.

**If your Power Platform and Dynamics 365 environments are hosted in the EU Data Boundary,
we use an Azure OpenAI endpoint in the same boundary.

Learn more about EU Data Boundary in What is the EU Data Boundary?.

Turn on data movement, Bing search, and

Microsoft 365 services for Copilots and generative
AI features
To turn on data movement across regions, Bing search, and Microsoft 365 services for Copilots
and generative AI features, you must consent to the terms of use in the Power Platform admin
center. To grant consent, you must be a Power Platform administrator or Dynamics 365
administrator.

New admin center

1. Sign in to the Power Platform admin center .

2. In the navigation pane, select Manage.

3. In the Manage pane, select Environments. The Environments page is displayed.

4. Select the name of your environment. Details about your environment are displayed.

5. In the Generative AI features card, select Edit. The Generative AI features pane is
displayed.

6. Review the terms of use and select the Move data across regions checkbox.

７ Note

The Move data across regions checkbox isn't displayed for US and government
cloud regions.

When the Move data across regions checkbox is selected, your inputs (prompts) and
outputs (results) might move outside of your region to the location where the
generative AI feature is hosted, as described in the preceding table.

Moving data across regions only happens if the required model isn't deployed
locally, if capacity is maxed out as overflow, or if there is a reliability-impacting
issue with the local model.
Microsoft doesn't log, store, or retain any input or output data during this
process. There is no persistence of the data.

For Core Online Services, allowing data movement across regions with this toggle
doesn't impact the commitments made in the Product Terms regarding storage of
Customer Data at rest. Learn more in Regions where data is processed for Copilots
and generative AI features.

７ Note
 Data movement that occurred while your environment was allowed to move
data across regions can't be reversed by clearing the Move data across regions
checkbox.

7. Review the terms of use and select the Bing search checkbox.

When the Bing search feature is turned on, your agent in Microsoft Copilot Studio
can use the data sources you provided, but it can use Bing's APIs to index the results
better and find the best answer from within your data sources. Learn more in
Generative answers.

７ Note

If the Move data across regions checkbox is displayed in the Generative AI

features pane, you must have it already selected in order to select the Bing
search checkbox.

8. Review the terms of use and select the Microsoft 365 services checkbox.

When the Microsoft 365 services feature is turned on, users can use features
powered by Microsoft 365 services.

To learn more about how the Microsoft 365 services feature affects Copilot Studio,
go to Manage activity data powered by Microsoft 365 services, Review agent activity,
and View advanced analytics in Microsoft Viva Insights. For information about data
locations, go to Data locations in Copilot Studio.

７ Note

If the Move data across regions checkbox is displayed in the Generative AI

features pane, you must have it already selected in order to select the Microsoft
365 services checkbox.

9. Select Save.

Copilots and generative AI features that depend on

data movement across regions
The following table lists Copilots and generative AI features that depend on the Move data
across regions checkbox.

When the Move data across regions checkbox is selected, these features work at their best,
allowing use of other region capacity when needed.

When the Move data across regions checkbox isn't selected, no data is sent outside of the
region, so depending on the in region capacities, some of these features won’t work.

More Copilots and generative AI features will be available in the future.

ﾉ Expand table

Product Feature Available Documentation

in GCC?

Dynamics 365 Copilot No Manage Copilot features in Customer Service

Customer
Service

Dynamics 365 Copilot No Copilot in Dynamics 365 Sales overview

Sales

Dynamics 365 Copilot No Customer Insights - Journeys: Give consent to use

Customer Copilot in Customer Insights - Journeys
Insights Customer Insights - Data: Give consent to use
Copilot in Customer Insights - Data

Microsoft Generative AI in Yes AI-based copilot authoring overview and

Copilot Studio copilots Configure data movement for Copilot Studio
generative AI features outside the United States

Microsoft Excel to table for No Upload an Excel file (preview)

Dataverse new makers

Power Apps Build apps No Build apps through conversation

through
conversation

Power Apps Describe a new No Describe the new table

table

Power Power Automate Yes Create your first cloud flow using Copilot
Automate designer Copilot

Power Pages Copilot No Overview of AI-powered and Copilot features in

Power Pages (preview)

AI Builder AI Prompts Yes Overview of Prompts

Languages availability
Learn more about the languages that are supported in the Copilot international availability
report .

Frequently asked questions (FAQ)

Is it possible to modify the "Move data across regions"

checkbox at scale across all my environments?
Yes, you can use the Generative AI settings environment rule to control this at scale. Learn
more in Rules.

What features are turned off when you clear the “Move data
across regions” checkbox?
The Move data across regions checkbox isn't intended to turn off Copilots and generative AI
features. When you clear the Move data across regions checkbox, it may turn off some
features that require data movement. As we add new capacities to new regions, these features
may work with in region capacity at some point. Use feature-dedicated controls to turn off
unwanted features.

Why do I need to select the “Move data across regions”

checkbox if my environment has in region capacity?
Some regions may have limited capacity, or no capacity at all. To ensure availability of Copilots
and generative AI features, we may need to move the data outside of the region for
processing.

Why does the “Move data across regions” checkbox not

appear in some of my environments?
If your environment is in a region that has full in region capacity, the Move data across regions
checkbox doesn't appear.

Related information
Legal terms
Last updated on 12/05/2025
Responsible AI FAQs for Microsoft Power
Platform
05/29/2025

An AI system includes not only the technology, but also the people who use it, the people
affected by it, and the environment in which it's deployed. Microsoft's Responsible AI FAQs are
intended to help you understand how AI technology works, the choices system owners and
users can make that influence system performance and behavior, and the importance of
thinking about the whole system, including the technology, the people, and the environment.
You can use Responsible AI FAQs to better understand specific AI systems and features that
Microsoft develops.

Responsible AI FAQs are part of a broader effort to put Microsoft's AI principles into practice.
To find out more, see Microsoft AI principles .

AI-driven features in this app

This app contains a growing list of AI-driven features. To learn about the capabilities and
impact of specific features, select a feature name from the list.

Copilot data security and privacy

Copilot data sharing
Use Copilot to generate deployment notes in pipelines

Related content
Responsible AI FAQs for Power Apps
Responsible AI FAQs for Power Automate
Responsible AI FAQs for Power Pages
FAQ for Copilot data security and privacy
for Dynamics 365 and Power Platform
05/29/2025

Copilot for Dynamics 365 and Power Platform features follow a set of core security and privacy
practices and the Microsoft Responsible AI Standard . Dynamics 365 and Power Platform data
is protected by comprehensive, industry-leading compliance, security, and privacy controls.

Copilot is built on Microsoft Azure OpenAI Service and runs completely within the Azure cloud.
Azure OpenAI offers regional availability and responsible AI content filtering. Copilot uses
OpenAI models with all the security capabilities of Microsoft Azure. OpenAI is an independent
organization. We don't share your data with OpenAI.

Copilot features aren't available in all Azure geographies and languages. Depending on where
your environment is hosted, you might need to allow data movement across geographies to
use them. For more information, see the articles listed under Data movement across
geographies.

What happens to my data when I use Copilot?

You are in control of your data. Microsoft doesn't share your data with a third party unless
you've granted permission to do so. Further, we don't use your customer data to train Copilot
or its AI features, unless you provide consent for us to do so. Copilot adheres to existing data
permissions and policies, and its responses to you're based only on data that you personally
can access. For more information about how you can control your data and how your data is
handled, see the articles listed under Copilot in Dynamics 365 apps and Power Platform.

Copilot monitors for abusive or harmful uses of the service with transient processing. We don't
store or conduct eyes-on review of Copilot inputs and outputs for abuse monitoring purposes.

How does Copilot use my data?

Each service or feature uses Copilot based on the data that you provide or set up for Copilot to
process.

Your prompts (inputs) and Copilot's responses (outputs or results):

Are NOT available to other customers.

Are NOT used to train or improve any third-party products or services (such as OpenAI
models).
 Are NOT used to train or improve Microsoft AI models, unless your tenant admin opts in
to sharing data with us. Learn more at FAQ for optional data sharing for Copilot AI
features in Dynamics 365 and Power Platform.

Learn more about Azure OpenAI Service data privacy and security. To learn more about how
Microsoft protects and uses your data more generally, read our Privacy Statement .

Where does my data go?

Microsoft runs on trust. We're committed to security, privacy, and compliance in everything we
do, and our approach to AI is no different. Customer data, including Copilot inputs and
outputs, is stored within the Microsoft Cloud trust boundary.

In some scenarios, such as features powered by Bing and third-party copilot plug-ins, customer
data might be transmitted outside the Microsoft Cloud trust boundary.

Can Copilot access encrypted content?

Data is provided to Copilot based on the access level of the current user. If a user has access to
encrypted data in Dynamics 365 and Power Platform, and the user provides it to Copilot, then
Copilot can access it.

How does Copilot protect customer data?

Microsoft is uniquely positioned to deliver enterprise-ready AI. Copilot is powered by Azure
OpenAI Service and complies with our existing privacy, security, and regulatory commitments
to our customers.

Built on Microsoft's comprehensive approach to security, privacy, and compliance.

Copilot is integrated in Microsoft services like Dynamics 365 and Power Platform and
inherits their security, privacy, and compliance policies and processes, such as multifactor
authentication and compliance boundaries.

Multiple forms of protection safeguard organizational data. Service-side technologies

encrypt organizational content at rest and in transit for robust security. Connections are
safeguarded with Transport Layer Security (TLS), and data transfers between Dynamics
365, Power Platform, and Azure OpenAI occur over the Microsoft backbone network,
ensuring both reliability and safety. Learn more about encryption in the Microsoft Cloud.

Architected to protect your data at both the tenant and the environment level. We
know that data leakage is a concern for customers. Microsoft AI models are not trained
 on and don't learn from your tenant data or your prompts, unless your tenant admin has
opted in to sharing data with us. Within your environments, you can control access
through permissions that you set up. Authentication and authorization mechanisms
segregate requests to the shared model among tenants. Copilot utilizes data that only
you can access, using the same technology that we've been using for years to secure
customer data.

Are Copilot's responses always factual?

As with any generative AI, Copilot responses aren't 100% factual. While we continue to improve
responses to fact-based inquiries, you should still use your judgment and review the output
before you send it to others. Copilot provides helpful drafts and summaries to help you do
more, but it's fully automatic. You always have a chance to review the AI-generated content.

Our teams are working to proactively address issues such as misinformation and
disinformation, content blocking, data safety, and promotion of harmful or discriminatory
content, in line with our responsible AI principles .

We also offer guidance in the user experience to reinforce the responsible use of AI-generated
content and suggested actions.

Instructions and prompts. When you use Copilot, prompts and other instructional
elements remind you to review and edit responses as needed and to manually check
facts, data, and text for accuracy before you use the AI-generated content.

Cited sources. Where applicable, Copilot cites its information sources, whether public or
internal, so that you can review them yourself to confirm its responses.

For more information, see the Responsible AI FAQ for your product on Microsoft Learn.

How does Copilot block harmful content?

Azure OpenAI Service includes a content filtering system that works alongside core models.
The content filtering models for the Hate & Fairness, Sexual, Violence, and Self-harm categories
have been specifically trained and tested in various languages. This system works by running
both the input prompt and the response through classification models that are designed to
identify and block the output of harmful content.

Hate and fairness-related harms refer to any content that uses pejorative or discriminatory
language based on attributes like race, ethnicity, nationality, gender identity and expression,
sexual orientation, religion, immigration status, ability status, personal appearance, and body
size. Fairness is concerned with making sure that AI systems treat all groups of people
equitably without contributing to existing societal inequities. Sexual content involves
discussions about human reproductive organs, romantic relationships, acts portrayed in erotic
or affectionate terms, pregnancy, physical sexual acts, including those portrayed as an assault
or a forced act of sexual violence, prostitution, pornography, and abuse. Violence describes
language related to physical actions that are intended to harm or kill, including actions,
weapons, and related entities. Self-harm language refers to deliberate actions that are intended
to injure or kill oneself.

Learn more about Azure OpenAI content filtering.

Does Copilot block prompt injections ( jailbreak

attacks)?
Jailbreak attacks are user prompts that are designed to provoke the generative AI model into
behaving in ways it was trained not to or breaking the rules it's been told to follow. Services
across Dynamics 365 and Power Platform are required to protect against prompt injections.
Learn more about jailbreak attacks and how to use Azure AI Content Safety to detect them.

Does Copilot block indirect prompt injections

(indirect attacks)?
Indirect attacks, also referred to as indirect prompt attacks or cross-domain prompt injection
attacks, are a potential vulnerability where third parties place malicious instructions inside of
documents that the generative AI system can access and process. Services across Dynamics 365
and Power Platform are required to protect against indirect prompt injections. Learn more
about indirect attacks and how to use Azure AI Content Safety to detect them.

How does Microsoft test and validate Copilot

quality, including prompt injection protection and
grounded responses?
Every new Copilot product and language model iteration must pass an internal responsible AI
review before it can be launched. Before release, we use a process called "red teaming" (in
which a team simulates an enemy attack, finding and exploiting weaknesses to help the
organization improve its defenses) to assess potential risks in harmful content, jailbreak
scenarios, and grounded responses. After release, we use automated testing and manual and
automated evaluation tools to assess the quality of Copilot responses.
How does Microsoft enhance the foundation
model and measure improvements in grounded
responses?
In the context of AI, especially AI that deals with language models like the one that Copilot is
based on, grounding helps the AI generate responses that are more relevant and make sense in
the real world. Grounding helps ensure that the AI's responses are based on reliable
information and are as accurate and relevant as possible. Grounded response metrics assess
how accurately the facts stated in the grounding content that's provided to the model are
represented in the final response.

Foundation models like GPT-4 are enhanced by Retrieval Augmented Generation (RAG)
techniques. These techniques allow the models to use more information than they were trained
on to understand a user's scenario. RAG works by first identifying data that is relevant for the
scenario, similar to how a search engine identifies web pages that are relevant for the user's
search terms. It uses multiple approaches to identify what content is relevant to the user
prompt and should be used to ground the response. Approaches include searching against
different types of indexes, such as inverted indexes using information retrieval techniques like
term matching, or vector indexes using vector distance comparisons for semantic similarity.
After it identifies the relevant documents, RAG passes the data to the model along with the
current conversation, giving the model more context to better understand the information it
already has and generate a response that's grounded in the real world. Finally, RAG checks the
response to make sure that it's supported by the source content it provided to the model.
Copilot generative AI features incorporate RAG in multiple ways. One example is chat with data
using, where a chatbot is grounded with the customer's own data sources.

Another method for enhancing foundational models is known as fine-tuning. A large dataset of
query-response pairs is shown to a foundational model to augment its original training with
new samples that are targeted to a specific scenario. The model can then be deployed as a
separate model—one that's fine-tuned for that scenario. While grounding is about making the
AI's knowledge relevant to the real world, fine-tuning is about making the AI's knowledge
more specific to a particular task or domain. Microsoft uses fine-tuning in multiple ways. For
example, we use Power Automate flow creation from natural language descriptions provided
by the user.

Does Copilot meet requirements for regulatory

compliance?
Microsoft Copilot is part of the Dynamics 365 and Power Platform ecosystem and meets the
same requirements for regulatory compliance. For more information about the regulatory
certifications of Microsoft services, go to Service Trust Portal . Additionally, Copilot adheres to
our commitment to responsible AI, which is put into action through our Responsible AI
Standard . As regulation in AI evolves, Microsoft continues to adapt and respond to new
requirements.

Learn more about Dynamics 365, Power Platform, and Copilot availability, customer data
locations, and compliance with global, regional, and industry-specific requirements for
managing data .

Learn more

Copilot in Dynamics 365 apps and Power Platform

ﾉ Expand table

Product Feature Managed How to turn the feature off

Environments
required?

AI Builder Scenarios in preview No Scenarios in preview

Copilot Studio AI general knowledge No Copilot Studio security and

governance

Copilot Studio Create and edit topics with No Copilot Studio security and
Copilot governance

Copilot Studio Generative actions No Copilot Studio security and

governance

Copilot Studio Generative answers No Copilot Studio security and

governance

Dynamics 365 All (See the full list at No Activate features

Business [Link]/bcAI .)
Central

Dynamics 365 Create segments with Copilot No Customer Insights - Data has its
Customer for Customer Insights - Data own flag for all its Copilot features
Insights - Data (preview) by Azure OpenAI.

Learn more: Give consent to use

Copilot in Customer Insights -
Data
Product Feature Managed How to turn the feature off
Environments
required?

Dynamics 365 Data prep report overview No Customer Insights - Data has its
Customer (preview) own flag for all its Copilot features
Insights - Data by Azure OpenAI.

Learn more: Give consent to use

Copilot in Customer Insights -
Data

Dynamics 365 Get answers to questions No Customer Insights - Data has its
Customer about capabilities from own flag for all its Copilot features
Insights - Data Copilot (preview) by Azure OpenAI.

Learn more: Give consent to use

Copilot in Customer Insights -
Data

Dynamics 365 Have a dialog with data using No Customer Insights - Data has its
Customer Copilot in Customer Insights own flag for all its Copilot features
Insights (Data) by Azure OpenAI.

Learn more: Give consent to use

Copilot in Customer Insights -
Data

Dynamics 365 View system configuration No Customer Insights - Data has its
Customer own flag for all its Copilot features
Insights - Data by Azure OpenAI.

Learn more: Give consent to use

Copilot in Customer Insights -
Data

Dynamics 365 Copilot helps you learn and No Whether this copilot is available in
Customer do more (review) your environment is determined
Insights - by Power Platform administrator
Journeys settings. Learn how to add Copilot
for model-driven apps.

This capability is "app copilot in

Customer Insights - Journeys" and
that's why it's enabled in Power
Platform admin center. Learn
more: Responsible AI FAQ
Product Feature Managed How to turn the feature off
Environments
required?

Dynamics 365 Create journeys using AI No Customer Insights - Journeys has

Customer assistance its own flags for Copilot features.
Insights -
Journeys Learn more: Give consent to use
Copilot in Customer Insights -
Journeys

Dynamics 365 Refresh and perfect your No Customer Insights - Journeys has
Customer message its own flags for Copilot features.
Insights -
Journeys Learn more: Give consent to use
Copilot in Customer Insights -
Journeys

Dynamics 365 Style your emails with AI- No Customer Insights - Journeys has
Customer assisted themes its own flags for Copilot features.
Insights -
Journeys Learn more: Give consent to use
Copilot in Customer Insights -
Journeys

Dynamics 365 Target the right customers No Customer Insights - Journeys has
Customer using query assist its own flags for Copilot features.
Insights -
Journeys Learn more: Give consent to use
Copilot in Customer Insights -
Journeys

Dynamics 365 Use AI to kickstart email No Customer Insights - Journeys has

Customer creation its own flags for Copilot features.
Insights -
Journeys Learn more: Give consent to use
Copilot in Customer Insights -
Journeys

Dynamics 365 Use images in your content No Customer Insights - Journeys has
Customer its own flags for Copilot features.
Insights -
Journeys Learn more: Give consent to use
Copilot in Customer Insights -
Journeys

Dynamics 365 Compose an email No Manage Copilot features in

Customer Customer Service
Service
 Product Feature Managed How to turn the feature off
Environments
required?

Dynamics 365 Draft a chat response No Manage Copilot features in

Customer Customer Service
Service

Dynamics 365 Respond to questions No Manage Copilot features in

Customer Customer Service
Service

Dynamics 365 Summarize a case and No Manage Copilot features in

Customer conversation Customer Service
Service

Power Apps Build apps through No Manage feature settings

conversation

Power Apps Copilot assistance for form No Manage feature settings

filling in model-driven apps

Power Apps Draft well-written, input text No, premium Draft well-written, input text with
with Copilot user license Copilot

Power Apps Excel to Table No Manage feature settings

Power Apps Use natural language to edit No Manage feature settings

an app using the Copilot
panel

Power Copilot in cloud flows on the No Contact support to run a

Automate Home page and in the PowerShell script.
designer (See Get started with
Copilot in cloud flows for
details.)

Power Pages All (See Copilot overview in No Turn off Copilot in Power Pages
Power Pages for details.)

Learn more at FAQ for optional data sharing for Copilot AI features in Dynamics 365 and Power
Platform.

Regional and language availability

Copilot international availability

Data movement across geographies

 How data movement across regions works
Configure data movement across geographic locations for generative AI features outside
United States
Copilot data movement across geographies in Dynamics 365 Sales
Copilot data movement across geographies in Dynamics 365 Business Central

Security at Microsoft
Introduction to Azure security
Encryption in the Microsoft Cloud
Data, privacy, and security for Azure OpenAI Service – Azure AI services

Privacy at Microsoft
Microsoft Privacy Statement

Responsible AI
Microsoft Responsible AI Standard
Responsible AI FAQ for Microsoft Power Platform
Responsible AI FAQ for Dynamics 365
Responsible AI FAQs for Microsoft Copilot Studio
FAQ for optional data sharing for
Copilot AI features in Dynamics 365 and
Power Platform
Article • 01/22/2025

These frequently asked questions (FAQ) article describes information related to optional
data sharing to improve Dynamics 365 Copilot and Power Platform Copilot AI features
and how Microsoft responsibly uses your data.

What is data sharing for Copilot AI features?

Microsoft is constantly working to improve the quality of the new AI-powered Copilot
features for Dynamics 365 Copilot and Power Platform Copilot to generate outcomes
with better accuracy. One of the important ways to improve Copilot features is to better
understand users' inputs to the Copilot features, related outputs, and telemetry.
Enabling the Data sharing for Dynamics 365 Copilot and Power Platform Copilot AI
Features setting in the Power Platform admin center allows Microsoft to capture and
manually review customer data including, but not limited to, users' natural language
inputs, outputs, and related telemetry to build, improve, and/or validate Microsoft's
features, services, machine learning models, and related systems for Dynamics 365 and
Power Platform Copilot AI features.

How does it work?

You may opt in to participate by using the Power Platform admin center.

７ Note

This setting is only available for tenants located in the US region currently.

To opt in:

1. Sign in to the Power Platform admin center .

2. In the left pane, select Settings > Tenant Settings, and turn on Data sharing for
Dynamics 365 Copilot and Power Platform Copilot AI Features > Enable Data
Sharing toggle.
 3. Select Save.

７ Note

When this optional data sharing setting is off, we don't use customer data under
this program.

What are the benefits of opting in?

Sharing your data can benefit you in two ways:

Existing Copilot AI features will become more effective as the models learn from
and adapt to aggregate patterns observed in data shared through the program.
We may derive new models that power new AI features in Dynamics 365 and
Power Platform.

If I've opted in, how can I withdraw my

consent?
By default, the data sharing option is disabled for you. After you opt in, you can opt out
any time by going to the Settings > Tenant Settings page in the Power Platform admin
center and turning off the Data sharing for Dynamics 365 Copilot and Power Platform
Copilot AI Features toggle. More information: Tenant settings

What happens when I withdraw my consent?

You own your data. Microsoft uses your data only to provide the services we've agreed
upon and for the purposes that are compatible with providing those services. Your data
remains yours and we don't share it. If you leave this program, all your data is deleted
within 30 days of opting out. However, we may still use your data up to end of the 30-
day period.

Who has access to my data?

Access to customer data is strictly controlled. Your data can be viewed only by the
Microsoft employees who must view your data and have authorized access.
What operational factors and settings allow for
effective and responsible use of the system?
Your data can only be accessed by Microsoft personnel with elevated access
permissions. Your data is stored in your geographic data boundaries with a 30-day
retention policy.

What about data privacy?

All data is handled as per the Copilot data security and privacy guidelines explained in
FAQ for Copilot data security and privacy in Microsoft Power Platform.

What about Customer Lockbox and customer-

managed keys?
Customer Lockbox and customer-managed keys won't apply to the access and manual
review of customer data shared using this setting.

Related content
Manage tenant settings
FAQ for Microsoft Power Platform
FAQ for Dynamics 365

Feedback
Was this page helpful?  Yes  No

Provide product feedback

FAQ for use Copilot to generate
deployment notes in pipelines
05/31/2025

These frequently asked questions (FAQ) describe the AI impact of the use Copilot to generate
deployment notes with pipelines feature in Power Platform.

What's use Copilot to generate deployment notes

in pipelines?
AI-generated deployment notes is a feature in pipelines for Power Platform that allows you to
seamlessly generate deployment notes to provide more context to your deployment record.
The only steps are to review what AI has generated for you (prefilled in the Deployment notes
field), and continue to deploy.

What are the system’s capabilities?

This capability is powered by Azure OpenAI Service, which uses powerful language models.
These language models generate new text in English that looks and sounds like text written by
humans.

Using Azure OpenAI service as a foundation, deployment notes are generated in the form of a
solution overview, providing a concise solution description and an overview of its components.
These notes are based on component metadata such as name, description, and type.

What is the system’s intended use?

AI-generated deployment notes help admins approve and manage deployments in their
organization, providing insight into what a solution contains and its purpose. AI-generated
content might have mistakes. Make sure it's accurate and appropriate before using it.

How was use Copilot to generate deployment

notes in pipelines evaluated? What metrics are
used to measure performance?
Use Copilot to generate deployment notes in pipelines underwent substantial testing before
the feature was released in preview. If you encounter issues with the content being generated,
please submit feedback. Your feedback is used to improve Microsoft products and services. IT
admins for your organization can view and manage your feedback data.

For more information, go to: Data, privacy, and security for Azure OpenAI Service

What are the limitations of use Copilot to generate

deployment notes in pipelines? How can users
minimize the impact of the AI-generated
deployment notes in pipelines limitations when
using the system?
This capability is in the process of rolling out, and might not be available in your region yet.

This capability might be subject to usage limits or capacity throttling.

The following are requirements to access the feature:

This feature is supported in the following languages: English, Chinese (Simplified), Czech,
Danish, Dutch, Finnish, French, German, Greek, Italian, Japanese, Korean, Norwegian
(Bokmål), Polish, Portuguese (Brazil), Russian, Spanish, Swedish, Thai, and Turkish. Copilot
uses the language selected in Settings > Power Apps settings > Language in
[Link].

AI deployment notes must be enabled for your pipeline to use the Copilot leveraging AI
models. To enable the feature:

1. Go to your pipelines host environment > Deployment Pipeline

Configuration > Pipelines > and select the desired pipeline.

2. On the General settings page, under Pipeline Details, enable or disable AI

deployment notes.

More information: Use Copilot to generate deployment notes in pipelines.

What operational factors and settings allow for

effective and responsible use of the system?
Complete these tasks to make the most of this feature:

Name your solution components accurately.

Add descriptions to your solution components to give them more context.
See also
Use Copilot to generate deployment notes in pipelines