This article describes features that have been removed, or 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 have changed or been removed in each version of finance and operations apps.
Feature deprecation effective May 2024
Support for unregistered Microsoft account and external Microsoft Entra ID users
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?
If a Microsoft account or Microsoft Entra ID account isn't registered in your Microsoft Entra ID tenant, you won't be able to access finance and operations apps. You'll 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". The user will be 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
End of support date is targeted for May 2024.
Feature deprecation effective April 2024
Tokens 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 will result 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 will be removed by April 2024 for non-production environments and by May 2024 for production environments.
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 will no longer be authenticated. Finance and operations APIs will start to fail from these apps in deprecated environments. To review your onboarded applications, in finance and operations apps, go to System administration > Setup > Microsoft Entra applications. For information about how to review your onboarded applications, see Register your external application.
Replaced by another feature?
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. Note – If application onboarding isn't expected, remove that app or replace with a compliant app that has a client service principal in tenant.
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 non-production environments and by April 2024 for production environments.
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 will begin 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 has been 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 will stop 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.
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.
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 out-dated 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 has been identified as a potential security vulnerability. This 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 will expire 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 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 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
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 has been turned off starting in release 10.0.21. The removal of this setting is targeted for April 2022; however, the feature will stop 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 doesn'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 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 has been superseded by other Lifecycle Services-based services.
In order to reduce the overhead of operating, monitoring, and maintaining the index management by customers, this feature has been removed.
Replaced by another feature?
After this update, the index maintenance is performed by Microsoft services. 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 has been deprecated.
Replaced by another feature?
Users see their initials in a circle in the navigation bar instead. This is the same visual 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) have been 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 that are 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
This 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 has been 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 existing grid control is being replaced by the new grid control.
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 targeted to be deprecated by 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 has been 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 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 will be 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 has changed. Self-service no longer supports IP safe lists.
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.
Remove the invalid field reference from the table field group definition.
Recompile.
Make sure that any errors are addressed.
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
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 has been 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 is a usability issue because it 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 have 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
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.