Removed or deprecated platform features
This article describes removed features, or features that are planned for removal in platform updates of finance and operations apps.
- A removed feature is no longer available in the product.
- A deprecated feature isn't in active development and may be removed in a future update.
This list is intended to help you consider these removals and deprecations for your own planning.
Detailed information about objects in finance and operations apps can be found in the Technical reference reports. You can compare the different versions of these reports to learn about objects that are changed or removed in each version of finance and operations apps.
Feature deprecation effective October 2024
User Authentication Changes in Finance and Operations: Transition to Object ID and Tenant ID
| Reason for deprecation/removal | Finance and operations apps are transitioning to a more robust user identification method using Object ID and Tenant ID from Microsoft Entra ID. We're continuing our efforts to modernize and streamline user authentication in finance and operations apps. This migration to Object ID and Tenant ID is part of the ongoing deprecation of legacy authentication mechanisms, following recent changes such as the removal of support for unregistered Microsoft Account and external Entra ID users and the deprecation of non-Entra ID external user sign-in. This update aligns with the Microsoft Entra goal of providing secure adaptive access by using strong authentication and conditional access policies to protect data without compromising user experience. The changes also align with Microsoft's focus on unified identity management to centralize and streamline access for both cloud and on-premises environments. This ensures consistent security policies and better visibility and control for managing all organizational identities. |
| Replaced by another feature? | Yes. The new authentication approach uses the Object ID and Tenant ID that are recommended for enhanced reliability and consistency in user management. This transition is part of broader efforts to standardize identity management across the platform. |
| What do you need to do? | Step 1. Verify User Accounts in Microsoft Entra ID: Step 2. Review and Fix noncompliant Users: |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | Support for the existing user authentication method is being deprecated, with the transition to Object ID and Tenant ID. Rollout has started, with full deprecation expected by October 30, 2024. |
Disable storage account key access to finance and operations managed storage accounts
| Reason for deprecation/removal | Improve platform security, and disable storage account key access to finance and operations managed storage accounts. |
| Replaced by another feature? | Microsoft Entra ID–based authentication |
| What do you need to do? | When the Allow storage account key access option is disabled, any requests to the account that are authorized with Shared Key, including shared access signatures, will be denied. (Any shared access signature URL is generated by using GetSharedAccessSignature.)
Note: LBD and CHE environments remains unaffected. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | Rollout for the change begins in October 2024 in a phased manner. Changes will be backported to 10.0.41 (PU65) and all later releases. For more information, and for updates about this change, see Finance and operations storage account security updates. |
Migration from deprecated libraries – WindowsAzure.Storage and Microsoft.Azure.Storage to Azure.Storage.Blobs
| Reason for deprecation/removal | Improve platform security, and remove the dependency on deprecated NuGet packages:
|
| Replaced by another feature? | Use Azure.Storage.Common, Azure.Storage.Blobs, Azure.Storage.*, and Azure.Data.Tables. |
| What do you need to do? | Customers and independent software vendors (ISVs) should review their dependencies/customizations and make any necessary changes to move to the new libraries before release 10.0.43 (PU67) service updates. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | Phase 1: Release and feedback (October 2024–November 2024) The new code will be released to a selected group of users for beta testing. Feedback will be collected, and any necessary adjustments will be made. The code will be fully rolled out after all fixes are made. During this period, we'll continue to support the old package. Phase 2: Deprecation timeline for customers – release 10.0.43 – PU67 (March 2025) This phase is the timeline when customers must move to new libraries before release 10.0.43 (PU67) service updates (general availability approximately March 2025). Phase 3: Stop shipping old libraries in version 10.0.44 – PU68 (June 2025) In version 10.0.44 (PU68) service updates (June 2025), support for the old package will end. Therefore, we'll stop shipping the old libraries, and the old code will be removed after telemetry data is validated to ensure that customer scenarios aren't affected. For more information, see the service updates schedule. For updates, see Finance and operations storage account security updates. |
Platform is changing the authentication protocol from password based auth to Microsoft Entra ID based authentication for 10.0.39 and greater releases.
| Reason for deprecation/removal | Improve platform security and remove dependency on password-based authentication. |
| Replaced by another feature? | Microsoft Entra ID based authentication. |
| What do you need to do? | This change impacts the following set of functionalities. 1. The SQL Connection string acquired by third-party code that isn't using any platforms public API present in platform. Recommendation: Switch to public API rather than reading it directly from config. 2. Long-running transactions that run for several hours. Recommendation: Reduce the time the connection is opened and keep the transactions as short-lived as possible. NOTE: LBD and CHE environments still use password-based authentication. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | End of support date is Oct 2024 starting with 10.0.39 (PU63) and greater releases. |
Feature deprecation effective September 2024
End of support for sharing storage account connection strings via public API GetCsuStorageConnectionString
Public method Microsoft.Dynamics.Clx.ServicesWrapper.CloudInfrastructure::GetCsuStorageConnectionString() will be deprecated.
| Reason for deprecation/removal | Maintaining storage connection string usage is a security issue. We want a more secure approach for connecting to the storage account. |
| Replaced by another feature? | Microsoft Entra ID–based interaction with the storage account |
| What do you need to do? |
|
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | The rollout of this change is being done in phases, beginning with sandbox environments. The change will then be applied in production environments for tenants that were created after August 19, 2024. The full rollout is estimated in October 2024. Changes will be backported to 10.0.39 (PU63) and all later releases. The method will be fully deprecated for all finance and operations customers in 10.0.43 (PU67) service updates (March 2025). For more information, see the service updates schedule. For updates, see Finance and operations storage account security updates. |
Microsoft will no longer ship or support the Visual Studio extensions for finance and operations apps, Power Platform tools, and Visual Studio versions prior to 2022.
| Reason for deprecation/removal | We want to focus our attention on one platform, harvesting the benefits provided from the 64-bit platform. |
| Replaced by another feature? | Visual Studio 2022. |
| What do you need to do? | Install Visual Studio version 2022. |
| Product areas affected | Development for finance and operations apps, including the Unified Development experience, and development of plugins with the Power Platform Tools. |
| Deployment option | All |
| Status | This change is effective as of Platform update 65 and Dynamics 365 Finance version 10.0.41 and later. |
Feature deprecation effective August 2024
Support for unregistered Microsoft account and external Microsoft Entra ID users
Login will be blocked for unregistered Microsoft Account (MSA) and External Microsoft Entra ID users in Finance and Operation Apps
| Reason for deprecation/removal | To enhance the security and performance of finance and operations apps, we're announcing the deprecation of support for unregistered Microsoft account users and external Microsoft Entra users in finance and operations apps. |
| What is changing? | Users not registered as a member or guest in the Microsoft Entra ID tenant can't access the finance and operations applications. If you aren't registered you receive the following error message: "AADSTS50020: user account ' contoso@contoso.com;' from identity provider 'https://sts.windows.net/{tenant ID}/' doesn't exist in tenant '{tenant name}' and can't access the application '{application ID}'(Finance and operations environment name) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with different Microsoft Entra ID user account."During the initial rollout phase, access to user will be failing with the following error message: “You aren't authorized to log in with your current credentials. You'll be redirected to the login page in a few seconds. To troubleshoot login issues, please visit Invalid Users Guide” Later these users will be blocked at the Microsoft Entra ID Tenant level. This change doesn't affect Granular Delegated Admin Permissions (GDAP) or CSP users. The user is blocked at the Microsoft Entra ID tenant level. This change doesn't affect granular delegated admin permissions (GDAP) or CSP users. |
| What do you need to do? | If a user who isn't part of your Microsoft Entra requires access to finance and operations apps, that user must be added to the Microsoft Entra ID tenant as an external user or guest user. For more information, see B2B collaboration overview. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | This change reaches your environment beginning last week of September 2024. |
Feature deprecation effective July 2024
Azure Active Directory Graph to Microsoft Graph Migration
| Reason for deprecation/removal | To enhance platform security and compliance, we're deprecating Azure Active Directory Graph in finance and operations apps. |
| Replaced by another feature? | Microsoft Graph - To ensure the security and integrity of your system and data, we strongly encourage all our customers to migrate to the more secure Microsoft Graph for making graph calls. |
| What do you need to do? | We strongly recommend that any customers with dependencies on the GraphAPIClient class (responsible for making Azure Active Directory Graph calls) migrate to the MicrosoftGraphClient (responsible for making Microsoft Graph calls) as soon as possible to avoid service disruptions. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | The Support for Azure Active Directory Graph will end in 10.0.41/PU65. |
SharePoint integration authentication using a Microsoft-managed high-trust connection
| Reason for deprecation/removal | The authentication mechanism used to integrate to SharePoint is being removed. |
| Replaced by another feature? | An alternate authentication mechanism is available via the SharePoint user authentication feature. For more information about setup, including a one-time permission grant to the application at the tenant level, see Configure document management. Calling SharePoint as a user that isn't the currently logged in user is no longer supported. |
| Product areas affected | System administration |
| Deployment option | Microsoft-managed cloud environments |
| Status | The SharePoint user authentication feature is available in Dynamics 365 Finance version 10.0.40, and is mandatory in version 10.0.42. Migration to the new SharePoint authentication must occur by February 28, 2025, at which time the current SharePoint connection stops working. |
Feature deprecation effective April 2024
Token resource or audience without an environment URL in finance and operations apps
| Reason for deprecation/removal | To enhance security compliance, we're deprecating the use of tokens that aren't acquired with the resource or audience that's set as the environment URL in finance and operations apps. |
| Replaced by another feature? | To ensure the security and integrity of your system and data, we strongly encourage all our customers to ensure that tokens are acquired only with the resource or audience that's set as the environment URL. Failure to comply with this requirement results in API calls in finance and operations apps beginning to fail. We encourage all developers and administrators to update their token acquisition processes accordingly to avoid any disruption in API functionality. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | To enhance security compliance, support for tokens with an audience claim value other than the environment URL is removed by April 2024 for nonproduction environments and by May 2024 for production environments. Platform update 63 and Dynamics 365 finance version 10.0.39 and later. |
To troubleshoot unauthorized 401 errors, see Check token compliance.
Multitenant apps without a service principal in the Microsoft Entra ID tenant
| Reason for deprecation/removal | Multitenant apps that don't have a client service principal have been recognized as vulnerable, because 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 is no longer authenticated. Finance and operations APIs will start to fail from these apps in deprecated environments. |
| Replaced by another feature? | No. To ensure the security and integrity of your system and data, we strongly encourage all our customers to provision the multitenant apps in their Microsoft Entra ID tenant. For more information, see Create an enterprise application from a multitenant application. If application onboarding isn't expected, remove that app or replace with a compliant app that has a client service principal in tenant. |
| What do you need to do? | Step 1. Review your onboarded applications: Step 2. Provision Application Service Principal: Step 3. Review the configured Endpoint: |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | Support for app-only tokens by multitenant apps that don't have a service principal ID will be removed by February 2024 for nonproduction environments and by April 2024 for production environments. Platform update 63 and Dynamics 365 finance version 10.0.39 and later |
To troubleshoot unauthorized 401 errors, see Check token compliance.
Feature deprecation effective March 2024
Non Microsoft Entra ID external user sign-in
| Reason for deprecation/removal | We're discontinuing onboardings for all users, both Service to Service and Interactive, who aren't present in the Microsoft Entra ID tenant associated with your Finance and Operations environment. Microsoft has flagged this access method as a security concern. For more information, see Manually add a new user. |
| Replaced by another feature? | No, to ensure compliance among existing users, you must either extend invitations to users with the same email addresses to your Microsoft Entra ID or remove these users from the Finance and Operations system, create new user accounts within your Microsoft Entra ID, and proceed to import them accordingly. For more information, refer How to create or delete users in Microsoft Entra ID - Microsoft Entra. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | The rollout for sandbox environments begins from Feb 2024 and for prod environments from March 2024. |
Feature deprecation effective February 2024
ISV Licenses generated using SHA1 algorithm (signature version 1)
| Reason for deprecation/removal | The SHA1 algorithm was widely recognized as vulnerable to security breaches due to its susceptibility to collision attacks. To address this security requirement, imports for ISV licenses that are generated using the SHA1 cryptographic algorithm are longer supported. |
| Replaced by another feature? | SHA256 - To ensure the security and integrity of your system and data, we strongly encourage all our customers to migrate to the more secure SHA256 algorithm for generating ISV licenses. |
Migrating to SHA256 is straightforward: You need to use signature version 2 or keep this field empty while generating license using AxUtil tool to generate a new license using SHA256. For more information, see Independent software vendor (ISV) licensing.
| Product areas affected | System Administration |
| Deployment option | All |
| Status | Support for SHA1 is removed by February 2024 (10.0.39/PU63) |
Feature deprecation effective January 2024
System Admin > Inquiries > User Log
| Reason for deprecation/removal | The Inquiries > User Log is a legacy page that was built for the older client/server architecture. The information on this page isn't always accurate and can be misleading. |
| Replaced by another feature? | In finance and operations apps, this information is captured in telemetry and Lifecycle Services has details. For more information, see Track user sign-ins. |
| Product areas affected | System Administration |
| Deployment option | All |
| Status | The User Log page will be removed by Jan 12 2024 (10.0.38/PU62) |
Exchange email provider
| Reason for deprecation/removal | The authentication mechanism that the Exchange email provider uses is being removed, and the Exchange provider never supported sovereign clouds. |
| Replaced by another feature? | Customers who use the Exchange email provider should migrate to the Microsoft Graph email provider. For more information, see Configure and send email. |
| Product areas affected | System administration |
| Deployment option | All |
| Status | The Exchange email provider stops sending emails as of September 15, 2024. |
Feature deprecation effective October 2022
Microsoft SQL Server 14.x or older
| Reason for deprecation/removal | We're discontinuing support for Microsoft SQL Server 14.x and older versions in Finance and Operations (Dynamics 365), as active support for 14.x ended in October 2022. Starting from 10.0.40 (PU 64), there may be SQL-related updates in FinOps that aren't compatible with older versions of MS SQL Server. |
| Replaced by another feature? | Yes, customers can use Microsoft SQL Server 15.x or higher with their Finance and Operations (Dynamics 365). |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | Deprecated. End of support date is targeted for 10.0.28 (PU 52), which went out of support on October 21, 2022. |
Feature deprecation effective August 2022
Lifecycle Services features deprecated in August 2022
As part of the One Dynamics One Platform work effort, the following Lifecycle Services features are deprecated.
| Feature name | Used with AX 2012? | Used with finance and operations apps? | Replaced by another feature? |
|---|---|---|---|
| Announcements | Yes | Yes | Yes: Banners exist on individual project and environment pages for notifications. |
| Configuration manager | Yes | No | No |
| Crash and dump analysis | Yes | No | No |
| Feedback and bugs | Yes | Yes | No |
| My subscription | Yes | Yes | No |
| Office 365 | Yes | Yes | Yes: Microsoft Entra ID or Microsoft admin portal. |
| Impact analysis | No | Yes | No |
| Total economic impact estimator | No | Yes | No |
| Service requests | No | Yes | Yes: Self-service deployments |
| SharePoint integration | Yes | Yes | No |
| Configuration and data manager | No | Yes | No |
| Process data packages | No | Yes | Yes: Data Import Export Framework (DIXF) |
| Environment upgrade | No | Yes | Yes: One Version service updates are available. |
| Infrastructure estimator | Yes | No | No |
| License sizing | Yes | No | No |
| Usage profiler | Yes | No | No |
| Customization analysis | Yes | No | No |
| System diagnostics | Yes | Yes | No |
| Business process modeler Visio management | Yes | Yes | No |
| AX 2012 cloud environment management | Yes | No | No |
| RDFE Azure connectors | Yes | Yes | No |
| AX 2012 versions | Yes | No | No |
| Work items stored in Lifecycle Services storage | Yes | Yes | No |
| Hotfix requests | Yes | Yes | No |
Transport Layer Security (TLS) RSA cipher suites
| Reason for deprecation/removal | The following list of cipher suites is removed to comply with our current security protocols. 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 TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA |
| Replaced by another feature? | Beginning January 2023, customers can only use our standard cipher suites. This change impacts your clients and servers that communicate with our servers. For example, it may impact your third party integrations that aren't adhering to our standard cipher suites. |
| Product areas affected | Finance and operations apps |
| Deployment option | Cloud deployments |
| Status | Deprecated. Customers must upgrade their servers before January 2023. For more information about configuring TLS Cipher Suite order, see Manage Transport Layer Security (TLS). |
Feature deprecation effective June 2022
Finance and operations (Dynamics 365) mobile application and mobile platform
| Reason for deprecation/removal | We're deprecating the finance and operations (Dynamics 365) mobile application and platform to consolidate to a single mobile platform, which is Power Apps. |
| Replaced by another feature? | Yes, mobile experiences over finance and operations app data can be built with Power Platform integration. For more information, see the blog post What’s happening to the Finance and Operations (Dynamics 365) mobile workspaces? and Building mobile experiences. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | Deprecated. End of support date is targeted for October 2024. |
Platform updates for version 10.0.29 of finance and operations apps
Panorama tab style
| Reason for deprecation/removal | Horizontally scrolling pages align to outdated layout patterns that have known usability and accessibility issues. |
| Replaced by another feature? | No, but other tab styles are still available. |
| Product areas affected | Web client |
| Deployment option | All |
| Status | Deprecated. |
Feature deprecation effective April 2022
XML URL resolution in Data management
| Reason for deprecation/removal | We're removing support for XML URL resolution since it was identified as a potential security vulnerability. This change means that external resources associated with XML files are no longer resolved. |
| Replaced by another feature? | No |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | Deprecated. |
Feature deprecation effective March 14, 2022
XSLT scripting in Data management
| Reason for deprecation/removal | The support for XSLT scripting in Data management is deprecated to improve security and data protection within finance and operations apps. |
| Replaced by another feature? | No, customers and ISVs should consider reimplementing their solutions based on X++ language, in place of XSLT scripting. |
| Product areas affected | Finance and operations apps |
| Deployment option | All |
| Status | Deprecated Exception: Customers who are currently using XLST scripting can continue to use it until they update to version 10.0.30 or later. For earlier versions, the exception expires effective January 31, 2023. Customers with this exception have received a notification in the Message center available in the Microsoft 365 Admin Center. |
Feature removal effective October 2021
Microsoft Azure SQL reports in Lifecycle Services
| Reason for deprecation/removal | All activities and monitoring are performed internally, by the platform, through automation. This change won't require any manual intervention. |
| Replaced by another feature? | Yes, there's now an automated system, which renders these capabilities obsolete. |
| Product areas affected | SQL reports: Current DTU, Current DTU Details, Get Lock Details, List of Current Plan Guide, Get List of Query IDs, Get the SQL query plan for a given Plan ID, Get query plans and execution status, Get throttle config, Get wait stats, List most expensive queries |
| Deployment option | Cloud deployment: Affects Microsoft-managed production environments and Tier 2 through Tier 5 sandbox environments. |
| Status | Removed |
Azure SQL actions in Lifecycle Services
| Reason for deprecation/removal | We're deprecating some SQL actions in Lifecycle Services. All activities and monitoring are performed internally, by the platform, through automation. This change won't require any manual intervention. |
| Replaced by another feature? | Yes, there's now an automated system, which renders these capabilities obsolete. |
| Product areas affected | SQL actions: Create a plan guide to force Plan ID, Create a plan guide to add table hints, Remove Plan guide, Disable/Enable page locks, and lock escalation, Update statistics on a table, Rebuild Index, Create Index |
| Deployment option | Cloud deployment: Affects Microsoft-managed production environments and Tier 2 through Tier 5 sandbox environments. |
| Status | Removed |
Feature deprecation effective October 2021
"Show related document attachments" feature
| Reason for deprecation/removal | The feature was returning unexpected results. |
| Replaced by another feature? | No, any further plans regarding this functionality is communicated through our standard release wave disclosure process. |
| Product areas affected | Web client - Document attachment experience |
| Deployment option | All |
| Status | Deprecated |
Platform updates for version 10.0.23 of finance and operations apps
OnDBSynchronize event
| Reason for deprecation/removal | There's no control to execute this event. |
| Replaced by another feature? | Yes, move existing methods subscribed to by the OnDBSynchronize event to a SysSetup extended class. |
| Product areas affected | Database synchronization |
| Deployment option | All |
| Status | Deprecated. Planned removal date is October 2022. |
SystemNotificationsManager.AddNotification API
| Reason for deprecation/removal | Microsoft requires more parameters when adding notifications. |
| Replaced by another feature? | Yes, the SystemNotificationsManager.AddSystemNotification() API. This API requires that you explicitly set ExpirationDateTime and RuleID for generated notifications. |
| Product areas affected | Web client |
| Deployment option | All |
| Status | Deprecated. Planned removal date is April 2023. |
Platform updates for version 10.0.21 of finance and operations apps
Skype for Business Online support
| Reason for deprecation/removal | Skype for Business Online was retired. For more information, see The Skype for Business Online service has retired. |
| Replaced by another feature? | Not currently, although we may consider adding presence from Teams in the future. |
| Product areas affected | Web client |
| Deployment option | All |
| Status | Deprecated. The Skype enabled setting was turned off starting in release 10.0.21. The removal of this setting is targeted for April 2022; however, the feature stops functioning after the Skype team shuts down the service. |
Feature deprecation effective August 2021
Microsoft Azure SQL reports in Lifecycle Services
| Reason for deprecation/removal | All activities and monitoring are performed internally, by the platform, through automation. This change won't require any manual intervention. |
| Replaced by another feature? | Yes, there's now an automated system, which renders these capabilities obsolete. |
| Product areas affected | SQL reports: Current DTU, Current DTU Details, Get Lock Details, List of Current Plan Guide, Get List of Query IDs, Get the SQL query plan for a given Plan ID, Get query plans and execution status, Get throttle config, Get wait stats, List most expensive queries |
| Deployment option | Cloud deployment: Affects Microsoft-managed production environments and Tier 2 through Tier 5 sandbox environments. |
| Status | Deprecated: Planned removal date is October 2021. |
Azure SQL actions in Lifecycle Services
| Reason for deprecation/removal | We're deprecating some SQL actions in Lifecycle Services. All activities and monitoring are performed internally, by the platform, through automation. This change won't require any manual intervention. |
| Replaced by another feature? | Yes, there's now an automated system, which renders these capabilities obsolete. |
| Product areas affected | SQL actions: Create a plan guide to force Plan ID, Create a plan guide to add table hints, Remove Plan guide, Disable/Enable page locks, and lock escalation, Update statistics on a table, Rebuild Index, Create Index |
| Deployment option | Cloud deployment: Affects Microsoft-managed production environments and Tier 2 through Tier 5 sandbox environments. |
| Status | Deprecated: Planned removal date is October 2021. |
Feature deprecation effective May 2021
Globalization portal in Lifecycle Services
| Reason for deprecation/removal | We're deprecating the Globalization portal in Lifecycle Services as this feature was superseded by other Lifecycle Services-based services. |
| Replaced by another feature? | Yes, Lifecycle Services Issue search and Dynamics regulatory alert submission service replace this feature. |
| Product areas affected | Globalization portal in Lifecycle Services |
| Deployment option | Cloud deployment |
| Status | Deprecated: Planned removal date is May 2022. |
Feature removed effective January 28, 2021
Batch job to handle SQL index defragmentation
| Reason for deprecation/removal | In order to reduce the overhead of operating, monitoring, and maintaining the index management by customers, this feature was removed. |
| Replaced by another feature? | After this update, Microsoft Services performs the index maintenance. This maintenance happens continuously without affecting the user workloads. |
| Product areas affected | Finance and operations apps |
| Deployment option | Cloud deployment - affects Microsoft-managed production environments and Tier 2 through Tier 5 sandbox environments. |
| Status | This feature is removed. |
Platform updates for version 10.0.17 of finance and operations apps
Visual Studio 2015
| Reason for deprecation/removal | To support the latest versions of Visual Studio, some changes have to be made to the X++ extensions for Visual Studio. These changes are incompatible with Visual Studio 2015. |
| Replaced by another feature? | Visual Studio 2017 replaces Visual Studio 2015 as the deployed and required version. |
| Product areas affected | Visual Studio development tools |
| Deployment option | All |
| Status | Deprecated: After you update to version 10.0.17, the previous X++ tools are removed from Visual Studio 2015, and the updated tools won't install on Visual Studio 2015. There isn't an impact on hosted builds. For build virtual machines, the build pipeline (build definition) needs to be manually updated to change the dependency from MSBuild 14.0 (Visual Studio 2015) to MSBuild 15.0 (Visual Studio 2017) as described in Update a legacy pipeline in Azure Pipelines. |
User avatar
| Reason for deprecation/removal | The user avatar that displays on the right side of the navigation bar was retrieved using an API from the Dynamics 365 header control, which was deprecated. |
| Replaced by another feature? | Users see their initials in a circle in the navigation bar instead. This same visual is currently used on development machines. |
| Product areas affected | Web client |
| Deployment option | All |
| Status | Removed as of version 10.0.17 |
Enterprise Portal (EP) deprecation
| Reason for deprecation/removal | The metadata artifacts associated with Dynamics AX 2012 Enterprise Portal (EP) are deprecated, as EP was never supported in the finance and operations apps. |
| Replaced by another feature? | No |
| Product areas affected | Web client |
| Deployment option | All |
| Status | Deprecated: All EP code is removed in the October 2021 release. |
Deprecation effective December 2020
Internet Explorer 11 support for Dynamics 365 is deprecated
| Reason for deprecation/removal | Effective December 2020, Microsoft Internet Explorer 11 support for all Dynamics 365 products and Dynamics Lifecycle Services is deprecated, and Internet Explorer 11 won’t be supported after August 2021. This change impacts customers who use Dynamics 365 products and Lifecycle Services designed to be used through an Internet Explorer 11 interface. After August 2021, Internet Explorer 11 won't be supported for such Dynamics 365 products and Lifecycle Services. |
| Replaced by another feature? | We recommend that customers transition to Microsoft Edge. |
| Product areas affected | All Dynamics 365 products and Lifecycle Services |
| Deployment option | All |
| Status | Deprecated: Internet Explorer 11 won’t be supported after August 2021. |
Platform updates for version 10.0.15 of finance and operations apps
Visual Studio add-in to apply metadata hotfixes
| Reason for deprecation/removal | Metadata hotfixes are no longer supported with the One Version service updates that were introduced in July 2018 with version 8.1. |
| Replaced by another feature? | Individual metadata hotfixes aren't available for supported versions. Cumulative quality updates are applied instead. |
| Product areas affected | Visual Studio add-ins |
| Deployment option | Development virtual machines |
| Status | With version 10.0.15, the add-in is no longer included in the Visual Studio tools. |
Platform updates for version 10.0.14 of finance and operations apps
Online users page
| Reason for deprecation/removal | The Online users page is a legacy page that was built for previous client/server architecture. The information on this page isn't always accurate, which can be confusing and misleading. |
| Replaced by another feature? | We'll provide a new page in a future update. As a workaround, use the table browser for the SysClientSessions table to view client sessions. |
| Product areas affected | System Administration |
| Deployment option | All |
| Status | This page will be removed in a future release. |
Platform updates for version 10.0.13 of finance and operations apps
Custom code defined in SSRS report properties
| Reason for deprecation/removal | In general, custom code offers limited benefits while at the same time, requires significant resourcing and compute to support. Custom code is primarily used by report authors to call public methods from a custom code assembly. However, the cloud-hosted service doesn't support references to custom assemblies for SSRS reports. |
| Replaced by another feature? | Report authors may choose to continue referencing public .NET APIs for Math, Conversion, and Format operations from any textbox expression. For more information, see Add Code to a Report (SSRS). |
| Product areas affected | Subset of application report designs that are defined in RDL and contain custom code. |
| Deployment option | All |
| Status | With version 10.0.13, the compiler begins issuing a warning for instances where custom code is detected in an SSRS report definition. To fix the issue, open the report design definition and remove all custom code artifacts. This warning will be replaced with a compiler error in a future update. |
Upgrade of three jQuery component libraries
| Reason for deprecation/removal | Three jQuery component libraries are being updated for security fixes and to maintain currency. |
| Replaced by another feature? | The following libraries are being affected: jQuery (to version 3.5.0 from version 2.1.4), jQuery UI (to version 1.12.1 from version 1.11.4), jQuery qTip (to version 3.0.3 from 2.2.1). Migration guidance was provided online by jQuery. |
| Product areas affected | Extensible controls, custom JavaScript code utilizing deprecated, or removed APIs. |
| Deployment option | All |
| Status | With version 10.0.13/Platform update 37, customers can optionally move to the latest libraries by enabling the "Upgrade three jQuery component libraries" feature. Moving to the new libraries are mandatory with the April 2021 release to allow time for migration of affected APIs. |
Existing grid control/forceLegacyGrid() API
| Reason for deprecation/removal | The new grid control replaces existing grid control. |
| Replaced by another feature? | The new grid control |
| Product areas affected | Web client |
| Deployment option | All |
| Status | The new grid control is mandatory with the October 2022 release (version 10.0.29). The forceLegacyGrid() API is currently still being honored if the old grid is still needed; however, this API is deprecated in the October 2023 release. When the deprecation of this API is announced, it's available for at least 12 months before no longer being available. |
Personalization without saved views
| Reason for deprecation/removal | The personalization subsystem was overhauled with the saved views feature, so that it has better performance and offers more capabilities. |
| Replaced by another feature? | Saved views |
| Product areas affected | Web client |
| Deployment option | All |
| Status | In version 10.0.13/Platform update 37, the saved views feature is generally available, and customers can optionally turn on this feature. The saved views feature becomes mandatory in the October 2021 release. |
Platform updates for version 10.0.12 of finance and operations apps
Grid or group control from extensions containing invalid field references
| Reason for deprecation/removal | The data group property on grid or group controls is used to automatically show all the fields of a field group. A grid or group control added by extension could contain fields that are no longer defined on the field group, or it might be missing fields defined on the field group. This group can cause inconsistent behavior at runtime. Platform updates for version 10.0.12 of finance and operations apps now categorize this issue as a compiler warning. To fix this issue, open the form extension and save it. |
| Replaced by another feature? | This compiler warning is replaced with a compiler error in a future update. |
| Product areas affected | Visual Studio development tools |
| Deployment option | All |
| Status | A compiler warning is introduced in platform updates for version 10.0.12 of finance and operations apps. |
Platform updates for version 10.0.11 of finance and operations apps
Explicit safe lists for self-service environments
| Reason for deprecation/removal | The process for moving IP to safe lists changed. Self-service no longer supports IP safe lists. |
| Replaced by another feature? | For more information, see Configuring Conditional Access. |
| Product areas affected | Security |
| Deployment option | Cloud |
| Status | Deprecated: This feature is fully deprecated for self-service deployments. |
Visual Studio 2015
| Reason for deprecation/removal | To support the latest versions of Visual Studio, some changes have to be made to the X++ extensions for Visual Studio. These changes are incompatible with Visual Studio 2015. |
| Replaced by another feature? | Visual Studio 2017 replaces Visual Studio 2015 as the deployed and required version. |
| Product areas affected | Visual Studio development tools |
| Deployment option | All |
| Status | Virtual machines deployed on version 10.0.13 (Platform update 37) or later contain Visual Studio 2017. Version 10.0.16 (Platform update 40) is the final release with support for Visual Studio 2015. Virtual machines with only Visual Studio 2015 can't update to version 10.0.17 (Platform update 41). |
Field groups containing invalid field references
| Reason for deprecation/removal | Field groups in table metadata definitions can contain field references that aren't valid. If these field groups are deployed, they can cause runtime failures in Financial Reporting and Microsoft SQL Server Reporting Services (SSRS). Platform update 23 introduced a compiler warning that enabled this metadata issue to be addressed. Platform updates for version 10.0.11 of finance and operations apps categorize this issue as a compiler error. To fix this issue, follow these steps.
|
| Replaced by another feature? | This compiler error permanently replaces the compiler warning. |
| Product areas affected | Visual Studio development tools |
| Deployment option | All |
| Status | Deprecated: The compiler warning is a compiler error in platform updates for version 10.0.11 of finance and operations apps. |
ISV licenses created by using the SHA1 hashing algorithm
| Reason for deprecation/removal | The process for creating independent software vendor (ISV) licenses has changed. For more information, see Independent software vendor (ISV) licensing. |
| Replaced by another feature? | Yes. Use Windows PowerShell to create licenses. |
| Product areas affected | Visual Studio development tools |
| Deployment option | All |
| Status | Deprecated: ISV licenses that were created by using the SHA1 hashing algorithm. This algorithm depended on certificates that were created by using the MakeCert utility, and this utility was deprecated. Deprecated: The use of SHA1 for security or hashing purposes. SHA1 ceases to function in early 2021. Therefore, it should no longer be used. Removed: Support for Transport Layer Security (TLS) 1.0 and TLS 1.1 incoming or outgoing requests. |
Platform update 32
Workflow request change dialog box no longer includes user selection drop-down list
| Reason for deprecation/removal | The user selection drop-down list was a security issue because the request for change could be sent to an unintended user. This usability issue forced the user to determine who the workflow originator was and manually select them. |
| Replaced by another feature? | No |
| Product areas affected | Workflow |
| Deployment option | All |
| Status | The user selection drop-down list was removed from the request change dialog box in Platform update 32. Request change requests are automatically sent to the originator as intended. For more information about this functionality, see Actions in workflow approval processes. |
Embedded drill-through links are no longer supported in paginated documents rendered by the cloud-hosted service
| Reason for deprecation/removal | Navigation URLs embedded in documents rendered by the service may contain sensitive business data. We're removing support for embedded drill-through links in documents as a security precaution to further protect customer's data. Users benefit from improved performance while interactively producing documents as a result of this change. |
| Replaced by another feature? | No |
| Product areas affected | Reporting |
| Deployment option | All |
| Status | This feature is actively being removed from the service. The modern client offers numerous options for producing views that include auto generated links to help navigating the application. Paginated documents rendered by the service are recommended for external communications that are emailed, archived, and printed for recipients. We improved the experience for previewing documents directly in the browser, which offers direct access to local printers. For more information, see Preview PDF documents with an embedded viewer. |
Previous announcements about removed or deprecated features
To learn more about removed or deprecated features in previous releases, see Removed or deprecated features in previous releases.