In order to deploy Microsoft Dynamics 365 for Finance and Operations in the cloud, the user must understand the environment and subscription that he is deploying to, who can perform which tasks, and the data and customizations that he needs to manage. It is recommended to sign up for the Full Microsoft FastTrack for Dynamics 365 to help speed deployment and implementation – it’s a program that provides training and consulting to help customers realize business value faster. If customer chooses to use the Essentials FastTrack program instead, he will be using the Implementation Project Methodology in Lifecycle Services (LCS) to help him manage the implementation project.
Microsoft assumes that all customers will follow a lifecycle similar to the following for all cloud deployments, and therefore need different environment topologies at each phase.
Customer or Partner subscription: The customer or partner brings their own Azure subscription and deploys Dynamics 365 for Finance and Operations environments to it, for evaluation and development purposes only. The customer or partner pays for the resources deployed to their Azure subscription based on the Azure price list.
Microsoft subscription: The customer purchases Dynamics 365 for Finance and Operations licenses which will then allow them to deploy environments to an Azure subscription which is managed by Microsoft, therefore, the customer has no separate Azure billing.
With each Enterprise offer, three environments are included by default:
Additional environments may be purchased as add-ons.
|Evaluation and analysis||Demo, one-box||Customer or partner subscription.|
|Customize||Dev/build, one-box||Microsoft subscription, partner/customer subscription, or local VM|
|User acceptance testing (UAT)||Tier-2 sandbox, multi-box environment||Microsoft subscription|
|Go live||Production, High Availability multi-box environment||Microsoft subscription|
1. Security and compliance:
Dynamics 365 for Operations is PA-DSS 3.1 certified which means that all communications between components are secured out-of-the-box.
All Dynamics 365 for Operations front-end virtual machines in Microsoft Azure are configured during deployment to only accept TLS 1.2.
2. Remote Desktop:
a. Microsoft managed environment:
Customers are now required to complete additional setup to connect to Dynamics 365 for Finance and Operations virtual machines (VMs) through Microsoft Remote Desktop (RDP). They must explicitly enable access (whitelist) from your organization’s IP address space.
b. Partner / Customer managed environment:
By default, Remote Desktop is enabled for all non-Microsoft managed environments. It is recommended that customers restrict access to any environments that belong to their subscriptions.
c. Windows Remoting (WinRM):
Windows Remoting (WinRM) is disabled on all environments. Although customer can enable WinRM on environments that belong to his subscriptions through Azure Portal, it is strongly recommended that customer should not do this.
The guaranteed uptime for Dynamics 365 for Finance and Operations is 99.5%. Planned downtime occurs once a month and lasts no longer than eight hours. Because the work completed during the downtime doesn’t always take eight hours, the support team will always communicate the estimated amount of time that your environments will be down.
4. Service availability:
Finance and Operations can be deployed into different Microsoft Azure datacenters using Dynamics Lifecycle Services (LCS). Azure is generally available in datacenters and geographical locations around the world. With Finance and Operations, customers can specify the region or datacenter where their customer data will be stored. Microsoft may replicate data to other regions for data durability, but they will not replicate or move customer data outside the geographical location.