Known issues with self-service deployment


Functionality noted in this article will be made available to users based on the geographic location recognized by Microsoft Azure.


As part of the One Dynamics One Platform work effort, some Microsoft Dynamics 365 Lifecycle Services (LCS) features have been deprecated. For more information, see Removed or deprecated platform features.

This article describes the known issues with self-service deployment.

Lifecycle Services (LCS)

Features not intended to be implemented

The following LCS features will not be implemented in self-service deployment.

  • System diagnostics - All data and functionality provided by system diagnostics today will be available through other features in the product and LCS.
  • Service requests - Service requests are being replaced with self-service actions.

Known issues in this release

Know issues are bugs that will be addressed in upcoming releases. Every 2 weeks there is a new release of LCS.

Finance and operations apps


Dynamics 365 Commerce is implemented in the modern deployment experience with the 10.0.10 release. For more information, see Create payment packaging for Application Explorer for self-service deployment.

Features not intended to be implemented

The following feature will not be implemented in self-service deployment.

  • Custom fonts - Custom fonts are not supported. For more information, see Document Reporting Service in Dynamics 365 applications.
  • Customizations related to user interface (UI) components on self service - Customizations that do not use the standard Financial Reporting or SQL Server Reporting Services (SSRS) in finance and operations apps often take a dependency on UI components of the operating system where the AOS runs. Example dependencies include Windows fonts, web browsers such as Internet Explorer, or custom PDF rendering. We do not ensure the host operating system will include any support for font infrastructure, web browsers, or any general UI components. The host operating system will change when migrating to self-service infrastructure. If you have such dependencies and have additional questions, please contact Microsoft Support.

Features no longer supported

The following feature is no longer supported with self-service deployment.


Customizations relying on FTP are not supported with self-service deployment. You should consider the following information:

  • We do not ensure that all outbound requests from an Application Object Server (AOS) are on a static IP address.

  • Until June 2021, we will ensure that all outbound requests during a particular AOS session will be on the same IP address. This can have implications for some processes, such as FTP. We recommend removing the use of FTP by using Power Apps to pull the files in and make API calls into finance and operations apps to import the files using the Data Integration framework. For more information, see Data entities integration overview. Some specific examples include:


For more information about deprecated features, see Removed or deprecated platform features and Removed or deprecated features from previous releases.