You can now quickly compose and deploy simple yet powerful Power Fx business logic inside Power Apps (make.powerapps.com) without requiring deep coding expertise, formerly called low-code instant plugins. By simplifying the creation of business logic, you reduce your reliance on pro developers, accelerating your development process, cost efficiency, and reusability while democratizing application development. The feature name update to functions from plug-ins closely aligns with the capabilities of the feature. Functions are server-side logic that can be reused across multiple apps and solutions within Power Apps, promoting consistency and scalability across the organization:

• Reusable components allow teams to standardize logic across multiple applications, reducing duplication of effort.
• Scalable solutions can be built incrementally, allowing for easy expansion and adaptation as business requirements grow.

Key features:

• Intuitive low-code formula language:
  • Familiar: Power Fx is a formula-based language, derived from Excel, making it intuitive and familiar for users who aren't traditional developers.
  • Easy to learn: Business users with minimal technical experience can create and manage functions with a minimal learning curve, reducing time to implement.
  • Rich functionality: Functions support a wide range of data manipulation, calculations, and conditional logic, allowing for diverse use cases.
• Dynamic updates:
  • Easily adjusted: Power Fx formulas can be easily adjusted as business needs evolve, providing agility to respond to changing market or organizational conditions.
• Reusability across applications:
  • Reusable functions: Once a Power Fx function is created, it can be shared across multiple applications within Power Apps, ensuring consistency in business logic across teams and departments.
  • Efficient scaling: Teams can save time by not having to re-create the same logic repeatedly across different solutions, reducing redundancies.

The security roles risk assessment tool is designed to elevate your business security and compliance standards. This feature automatically scans all security roles within Microsoft Dataverse, comparing each role's privileges against predefined baseline access levels. Noncompliant roles are promptly flagged, ensuring no potential security risks go unnoticed.

Key features and benefits:

• Automated scanning:

  • Feature: Event-driven automated scans of all security roles.
  • Benefit: Continuous monitoring ensures real-time identification of noncompliance, reducing manual oversight and improving efficiency.

• Noncompliance flagging:

  • Feature: Automatic flagging of roles that do not meet baseline policies.
  • Benefit: Immediate awareness of security risks allows for prompt action, mitigating potential threats quickly.

• Role owner empowerment:

  • Feature: Notifications to role owners with options to adjust privileges, request exceptions, or create custom profiles.
  • Benefit: Empowers your team to proactively address compliance issues, tailoring security to meet specific business needs while maintaining control.

• Custom risk assessment settings profiles:

  • Feature: Ability for role owners to create and submit custom profiles.
  • Benefit: Flexibility to accommodate unique business requirements without compromising security, with admin oversight to ensure adherence to policies.

• Admin review and approval facilitation:

  • Feature: Environment admins review and approve or reject requests.
  • Benefit: Maintains a high security standard by ensuring all changes undergo rigorous evaluation before implementation.

This feature will improve the maker experience so that citizen developers can easily spot unmanaged changes and work with them in bulk, either moving them to an unmanaged solution or removing them when not needed. These changes will ensure that citizen developers will have fewer issues with solutions from missing dependencies, unintentional layers that hide other solution changes, and significantly reduced effort to manage solutions.

These are the changes in solutions experiences in the Power Apps (make.powerapps.com):

• A new column Customized in solution views to indicate if a solution object has active customizations.
• Ability to multiselect and add components to another solution.
• Ability to multiselect and initiate removal of active customizations.
• Detecting missing dependencies during export and prompting the user to add unmanaged required components to the solution.

This feature will allow customers to provide an Azure DevOps source code repository to bind to the environment and solutions. Changes made to solution components will then be available to commit to the repository, and changes made to the source code from other environments or by direct modification of the files will be available to be pulled into the environment. Conflicts between those changes will be identified and resolved by the user.

Solution files for deployment to other environments are built directly from source control alone without having an environment present and deployed to other environments using our Power Platform tooling or by the user with pipelines in Power Platform. Customers can use advanced source management techniques as well as implement governance controls to ensure the quality of code and deployments to other environments are consistent with their policies and practices.

This feature will update the current Load to existing table option within standard dataflows in Power Platform. It will provide general UI updates and functionality to recommend what existing Dataverse tables new data should be mapped to. Once a target Dataverse table is selected, this feature will also provide recommendations for how the columns should be mapped and alert users to any type mismatches.

The link to Microsoft Fabric feature in Dataverse allows you to extend your data and insights in Dynamics 365 and Power Apps in Microsoft Fabric. Bring your own data into Fabric and combine, reshape, and aggregate data from Dataverse. Use Fabric tools, such as SQL, Spark, and dataflows to work with your data within Fabric. For example:

• Combine financial data from Dynamics 365 with financial data from other systems to derive consolidated insights.
• Merge historical data ingested into OneLake from legacy systems with current business data from Dynamics 365 and Dataverse.
• Combine weblogs and telemetry data from your website with product and order details from Dynamics 365.
• Apply machine learning and detect anomalies and exceptions within your data.

Insights aren't complete unless you can drive action and business processes. Bring insights you found in Fabric to build apps, drive business processes with Power Automate without data copy, no-ETL, or non-Microsoft integration tools.

With Dataverse virtual tables sourced with Fabric, your low-code app builders connect to data in OneLake and build apps with Power Apps to drive business actions. Additionally, with Power Pages, low-code makers can build external-facing websites and drive action from OneLake insights with partners, suppliers, and customers.

When a Power Platform admin modifies security roles that are system-predefined customizable or custom security roles previously imported by a Dataverse managed solution, these customizations can be overwritten by importing an update to the managed solution containing those security roles or when the system refreshes these security roles.

With this feature, the system predefined customizable security roles, custom security roles, and privileges will be merged with the updates to the security roles and privileges done by the Power Platform admin in an environment instead of overwriting the preexisting updates.

By default, when the App access control feature is activated, only approved apps can run in an environment, such as Dynamics 365 Sales or Dynamics 365 Customer Service. The local environment admin specifies which apps can be run by users in the environment. Unauthorized apps are blocked when a user tries to access them.

To help administration with selecting which apps to approve for use, we recommend that you turn on audit mode, for at least one week, to get the list of apps that your users are running in an environment. Using this audit log list, you can determine which apps you want to allow or block.

For apps that are allowed access, you can assign security roles to restrict who can run those apps in the environment. Only users assigned to the selected security role can run the apps.

Admins can navigate to the Security > Access controls page in the Power Platform admin center and then turn on the App access control feature. Admins can select the applications and the relevant security roles for which they want to allow access.

Key Features:

• Create copilots using solutions.
• Set my preferred solution in Copilot Studio.
• Create copilots and components using a preferred solution.
• Edit and extend copilots and components using a preferred solution.
• Deploy copilots and components using pipelines in Power Platform with a single click.
• Share copilots and components with a user or team.

The solution size increase to 1 GB feature will use chunking for both upload and download of solution files. We have new endpoints for these in the Microsoft Dataverse APIs.

The changes will affect both Microsoft Copilot Studio and Power Apps (make.powerapps.com) because Copilot Studio uses a Power App widget with the solutions page.

In the age of AI, it's essential for customers to integrate enterprise knowledge with foundational models to derive enterprise value. This encompasses enterprise data and data within application silos. Custom copilots equipped with knowledge enable straightforward grounding of large language model responses in enterprise data stored in Dataverse representing Dynamics 365 and Power Apps, providing users with relevant business insights, securely and in a compliant manner. This feature empowers makers to enrich their custom copilots with knowledge sources against enterprise data stored in Dataverse.

Allows comprehensive extension of agent components by:

• Whether or not to allow change of state for all agent components.

• New managed property to allow change of enable or disable state of agent components.

• Whether or not to allow addition of agent component type.

• New managed property to allow the addition of topics. - New managed property to allow addition of knowledge. - New managed property to allow addition of actions.

In this feature, we're allowing the virtual table to native table relationships. The following capabilities will be available.

Simple lookup CRUD operations:

• Filters (AND, OR) and conditions (all operators)
• Order by lookup field
• Multiple lookups (CRUD, filters, conditions, ordering)
• Paging

Expansion types of join (inner, left outer, ...):

• Link without relationship
• Retrieve all attributes
• Order by (expanded field, combined clauses)
• Filters (AND, OR) and conditions (all operators)
• Paging
• Multi-level expand
• One-to-many expand scenarios

Enterprise data as knowledge is crucial for business copilots. Enabling Microsoft Dataverse, containing data from Dynamics 365 as grounding data for declarative agents, built from Microsoft Copilot Studio will enable makers to build Copilot agents that understand your line of business (LoB) data. This capability already exists in custom agents built from Microsoft Copilot Studio. We are extending this to Copilot agents.

This feature allows you to navigate directly to a specific record inside a finance and operations application if you want to view additional information related to that record. When you access finance and operations records through Copilot for Microsoft 365 apps, you'll be provided with a link to see the key aspects of the record using adaptive cards. In case you want to perform more actions with the record, open the record from the link provided and select the link to navigate directly to the finance and operations record allowing you to view or modify it.

With the launch of the new certification experience in Build 2024 for Independent Software Vendors (ISVs) to certify copilot connectors (Power Platform based) developed in the maker portal and Microsoft Copilot Studio through Partner Center, you can get the following results:

• 99% certification efficiency gain by reducing the time from 40 days to 48 hours (P80).
• 100% automated partner vetting, ensuring the authenticity of ISVs and partners through OneVet on Partner Center.
• 72% simplification in submissions by reducing manually captured metadata and instead relying on attributes provided in package JSON.

For Ignite 2024, we extend the certification journey to bring all Microsoft Copilot Studio under one umbrella of certification in Partner Center to also accept copilot templates and copilot agents built by partners and ISVs for certification. This enables a starting point for our end customers and accelerates the ability for customers to install, extend, and deploy copilot agents to their environments.

All copilot extensibilities can be managed from a single place in Microsoft Copilot Studio, giving customer engagement app admins the needed governance controls to enrich the user experience for Copilot for Sales with plug-ins.

With this feature, it's now possible for various copilot administrators to also manage the extensibility of Copilot for Sales and other vertical copilots in Microsoft Copilot Studio. Customer engagement app admins managing Copilot for Sales can browse out-of-the-box plug-ins as well as plug-ins published by makers. Admins can enable or disable any plug-in for users.

Using Microsoft Copilot Studio, you can extend Copilot for Microsoft 365 by creating connector plug-ins using out-of-the-box or custom connectors. By following step-by-step prompts, users will be able to connect to a data source, specify the actions they would like copilots to be able to execute, provide sample questions for users to get started with their queries, and provide adaptive cards to present data in easy-to-understand formats.

As a finance and operations apps developer, you can create Copilot actions in X++ code and make them available and configurable in Copilot Studio and consume them in different copilot apps.

This feature helps developers of finance and operations such as apps to wrap, create, update, and delete functions of finance and operations as Copilot actions using X++ code. These copilot actions will start appearing in Copilot Studio for non-Microsoft app consumption and extensions. These actions can be published to copilots and invoked through copilots using Generative AI capabilities.

Power Platform services from Microsoft ship services, which include security roles and application users, frequently. These roles and applications are automatically documented on our Microsoft learn site with standard and consistent content. Customers can use Copilot in Bing to find the list of privileges in a security role and the differences between security roles without asking a local admin to get into a Dataverse environment to do that.

Actions created in Copilot Studio will be automatically saved in a solution at the time of creation. If you do not have a desired solution added, a new solution will be created with the name of the action. This feature simplifies the process for you to move actions across different environments.

When you need to transition to another environment, you can effortlessly export the solution by clicking the 'Export solution' button on the details page of the current environment. Subsequently, you can import the solution into the target environment directly from Copilot Studio. This streamlined process ensures that actions are easily transferable and maintain consistency across various environments.

Information workers are bombarded with huge amounts of data and spend considerable time reading and processing it daily. Much of this time is spent preparing to respond to inquiries.

With this feature, data can be easily summarized into information, responses can be prioritized based on urgency (sentiment), responses can be categorized (classifying), pertinent info can be extracted (email, phone), and replies can be generated by using Microsoft Dataverse copilot generative AI functions. This copilot AI information can be defined and extended as part of the record and can be queried using copilot.

Environment variables play a key role in the application lifecycle management (ALM) process, allowing for seamless movement of applications across different Power Platform environments. When creating a virtual table, you can now associate it with its own environment variable.

To take advantage of this functionality, simply select Use environment variables when choosing a connection for your data source during virtual table creation. This feature links the environment variable directly to the virtual table provider, offering flexibility to modify data sources when importing the virtual table into a new environment.

The environment variable for a virtual table contains references to a connection reference. During solution import into a target environment, the developer or maker can modify or edit the connection reference.

The new Snowflake connector allows seamless connection between Dataverse and Snowflake, allowing you to build model-driven or canvas apps with ease in Power Apps, as well as supporting interactive and dynamic data manipulation. You can create, update, delete, and retrieve items in Snowflake tables, providing a seamless experience for managing data. Key features include the ability to create Dataverse virtual tables from Snowflake and real-time data synchronization, and advanced data manipulation through custom SQL statements in Power Automate flows.

These capabilities provide you with immense value by improving data accessibility, enhancing your experience, and allowing more efficient data management. With the Snowflake connector, you can leverage the full potential of Power Platform to drive actionable insights and streamline your workflows.

Additionally, it's worth noting that this new connector is a significant upgrade, replacing the older Snowflake connector (deprecated) that has been in use for some time. As part of this transition, the old connector will be deprecated on May 26, 2025, ensuring that you benefit from the latest features and improvements offered by the new Snowflake connector.

• Virtualization of external data sources like SQL, Salesforce, SharePoint, Snowflake, Fabric, Oracle.
• Create one-to-many and many-to-one relationships between Dataverse native tables to virtual tables and vice versa.
• Create one-to-many and many-to-one relationships between two virtual tables.
• Sort and filter on virtual tables.

Feature benefits include:

• Allow production environment self-serve failover directly from Power Platform admin center.
• Self-serve disaster recovery drills.
• Self-serve failover with up to the minute last sync time (data loss) that customers can compare with their stated recovery point objective (RPO) and make an informed decision to failover or not.
• Self-serve failback that empowers the customer to determine whether and when to switch back to the primary location.

As part of the regular business processes with Microsoft Dataverse, users often delete records or transactions either manually or systematically, either planned or by accident, using system processes, single selection, multiple selections, and bulk deletion. Retrieving deleted data is hard and often records aren't always recoverable. To address this limitation, the recycle bin is available to recover table record data from any type of delete scenario within a specified configurable time frame, from both UI and through APIs/SDK.

This feature allows makers to create relationships between two virtual tables whose data source could be different or the same. It has these benefits:

• Allows the maker to create a one-to-many or many-to-one relationship between two virtual tables of any external source.
• Allows the maker to create sorting and filtering of these two virtual entities with relationships.

The tenant-to-tenant environment move feature empowers tenant administrators with the ability to self-serve and migrate their environments from a source tenant to a target tenant using PowerShell. This feature is designed to streamline the migration process, providing admins with greater control and flexibility.

By leveraging PowerShell, tenant admins can initiate and manage the migration process independently, without the need for extensive support or intervention.

You can use on-premises servers for the following services:

1. Server-side sync (for Exchange emails).
2. Outbound plug-ins.
3. Web (server-to-server) integration.
4. Environment discovery using the regional discovery service.

Dynamics 365 Customer Engagement (on-premises) computers and network can upgrade the TLS protocol from TLS 1.2 to TLS 1.3 to better secure communications over the internet.

TLS 1.3 simplifies and enhances security by using only three cipher suites with perfect forward secrecy (PFS) and authenticated encryption with additional data (AEAD). This streamlines the protocol and ensures robust security. Key improvements include:

• Privacy enhancements: Minimal cleartext protocol bits prevent protocol ossification and hide content length, reducing visible user information on the network.
• Confidential client authentication: Unlike previous versions, TLS 1.3 ensures client authentication is always confidential, eliminating the need for renegotiation and reducing round trips and CPU costs.

TLS 1.3 offers better security, privacy, and efficiency over TLS 1.2.

• Makers can virtualize SQL views in Microsoft Dataverse.
• Allows the maker to build retrieve multiple for these virtualized SQL views.
• Allows the maker to sort and filter on these virtualized SQL views in Dataverse.