43
Environment Planning for Finance and Operations implementations Rachel Profitt Peter Ryo Rich Black
Environment Planning
for
Finance and Operations
implementations
Rachel Profitt
Peter Ryo
Rich Black
1. Describe the key concepts relevant to environments for Dynamics 365 Finance
and Supply Chain Management2. Discuss how to incorporate the Common Data Service (CDS) into your
environment plan.
3. Help you build an environment plan that is adapted to your implementation4. Provide you guidance based on experiences from actual implementations
What it doesn’t cover
1. Detailed licensing aspects
2. Service requests and SLA related to the
environment management
2
Agenda 1. Glossary
2. Standard offer
3. Additional environments
4. Sample exercise
5. Other considerations and recommendations
6. Checklist and resources
3
Agenda: Topic 1: Glossary
1. Glossary
2. Standard offer
3. Additional environments
4. Sample exercise
5. Other considerations and recommendations
6. Checklist and resources
4
Agenda:
What?
Why?
5
➢
➢
➢
➢
➢
➢
➢
➢
➢
➢
➢ 6
Multiple
environments and
Data centers for
an Organization
• An organization can have a dedicated instance of the AAD tenant to host multiple applications such as Power apps, Dynamics 365 apps etc.
• Each application can be deployed as multiple environments and hosted in different Azure data centers.
Azure Active directory
ProdTest
Dev
TestDev
Prod
Dynamics 365 Finance and Operations
SandboxProd
Dynamics 365 Human
Resources
US Data center
ProdTest
Dev
TestDev
Prod
Dynamics 365 Finance and Operations
Japan Data center
Australia Data center
ProdTest
Dev
TestDev
Prod
Dynamics 365 Finance and Operations
SandboxProd
Dynamics 365 Project service
7
TestProd
Dynamics 365 Finance and Operations
Dev
No LCS
HR LCS
Proj Ops LCS
Fin Ops LCS
About Multiple
Projects in one AAD
➢
➢
➢
➢
8
➢
➢
➢
➢
➢
9
Continued
Finance and Operations Apps Glossary
Common Data Service Glossary
Environment type
➢
Default environment
➢
➢
Environment scope
➢
➢
Trial environment
➢
➢
10
Agenda: Topic 2: Standard Offer
1. Glossary
2. Standard offer
3. Additional environments
4. Sample exercise
5. Other considerations and recommendations
6. Checklist and resources
11
Agenda:
Finance and Operations Apps – Licensing Guide
PRODUCTION environment
SANDBOX environment: Standard Acceptance Testing
-------------------------------------------------------------
Additional instances• Sandboxes of various capacities can be purchased as optional Microsoft-
managed Add-ons.
• Single-server environments can be deployed to customer-managed Azure subscriptions.
See the Microsoft Dynamics 365 Licensing Guide for more information.add-ons
(1GB increments)
12
Common Data Service – Licensing Guide
PRODUCTION
SANDBOX
DEVELOPMENT
See the Microsoft Dynamics 365 Licensing Guide for more information.
See the Request limits and allocations page for more information.
13
Production Environment Provisioning
PRODUCTION is deployed:➢ after the Subscription Estimator is completed
➢ after Performance testing telemetry data is available
➢ after the Go-Live Readiness Assessment is completed and approved
➢ after the Customer has signed off on UAT results
➢ with access to services and servers limited to Dynamics Service Engineers (DSE)
Once deployed, PRODUCTION:➢ can be used to do a final round of validation
➢ can be rolled back using Point-In-Time restore (based on 28-day retention period for backups)
➢ is High-Availability and Disaster-Recovery enabled
1. Usage profile completed
2. Performance testing
telemetry data available
3. Go-Live Readiness
Assessment approved
4. PRODUCTION environment
sized and deployed
5. Mock cutover, final round of
validation
6. Cutover and Go-Live
14
Sandbox Environment Provisioning
Standard SANDBOX is:➢ a Tier-2 multi-server Standard Acceptance Test environment
➢ provisioned during onboarding
➢ not accessible using RDP. Access to services and servers limited to Dynamics Service Engineers (DSE)
➢ can be rolled back using Point-In-Time Restore (PITR) (based on 7-day retention period for backups)
CDS Sandbox is:➢ deployed on demand
➢ should be deployed to the same region as F&O
CDS availability may influence F&O region selectionhttps://docs.microsoft.com/en-us/power-platform/admin/regions-overview
https://docs.microsoft.com/en-us/dynamics365/get-started/availability
http://azuredatacentermap.azurewebsites.net/15
➢ Leverage tools likePsping orAzureSpeed.com
Selecting a data center for Production
16
You may deploy
environments to
different regions...
...but all environments
should be deployed to the
same region as Production.
Agenda: Topic 3: Additional Environments
1. Glossary
2. Standard offer
3. Additional environments
4. Sample exercise
5. Other considerations and recommendations
6. Checklist and resources
18
Agenda:
Environment Plan SampleF&O environment
CDS environment
Environment PurposeF&O
TierCDS Type
Standard
Subscription
Less
Complex
Project
More
Complex
Project
Test/ Training 2 Sandbox *
Production Sized Production *
Development 1 Development
Build 1** N/A
Golden Configuration 1 or 2 N/A
Data Migration 2+ N/A
Performance Testing 4 or 5 Sandbox
Training 2 or 3 Sandbox
System Integration Testing 2 or 3 Sandbox
Other/ Ad Hoc --- Trial or
Sandbox
19
*Only one CDS is included with your F&O subscription. change the environment type by following these instructions.
**Build environment may not be necessary if using build automation which leverages Microsoft-hosted build agents in Azure DevOps.
This applies to➢ F&O Tier-2 to Tier-5 sandbox environments and
Production environment
➢ All Common Data Service Environments
This means➢ Microsoft is maintaining the environment (e.g. OS
and security maintenance)
➢ Self Service Deployments supported
This applies to➢ F&O Tier-1 environments only
This means
➢ The customer and/or partner must maintain the environment
➢ Require either hardware (for the .VHD) or an Azure subscription (for Cloud-Hosted environments)
➢ Remote connection (.RDP) and administrative access available
20
About Self-Service Deployments
Self-Service Deployments can be found here
21
➢ All components (e.g. the AOS, the database, retail and FR) are installed on the same server
➢ Uses SQL Server
➢ Different architecture than PRODUCTION, made to maximize the efficiency of the development team
➢ Can be deployed in different ways (.VHD or Cloud-Hosted)
➢ Perform UAT on a Tier-1 environment
➢ Execute performance testing on a Tier-1 environment
➢ Components are installed on multiple servers
➢ Uses Azure SQL
➢ Same architecture as PRODUCTION despite a different sizing
➢ Are only standard/add-on environments and can’t be hosted under the customer/partner Azure subscription
➢ Perform UAT on a Tier-2 or higher environment
➢ Execute performance testing on a Tier-4 or higher
22
Capability Downloading a .VHDCloud-Hosted
Under your own Azure subscription
Public URL Not supported OK
Integration developmentExtra setup required
(e.g. run the admin user provisioning tool)OK
Azure DevOpsExtra setup required
(e.g. rename the computer)OK
Apply deployable packages from LCS
Manual through runbooks OK
Deploy data packages from LCS
Not supported OK
Maintenance Managed by the customer/partner Managed by the customer/partner
Cost model Hardware-related
Pay-as-you-go (if the environment is on for 8 hours, you pay for 8 hours)
Cost is based on selected Virtual Machine size, disk size and settings, and premium storage settings 23
Tier-2
Standard Acceptance Test
Tier-3
Premier Acceptance Test
Tier-4
Standard Performance Test
Tier-5
Premier Performance Test
Rely on your partner to adjust this baseline considering the specific business scenarios (type of users/complexity/volumes/…)
For more information refer to the Environment Planning page.
24
CDS Environment Strategy
Multiple business unit
dev environments using
shared test.
Dedicated environments for
critical or large project
Multiple short-lifecycle environments
for small-team dev or training
25
Agenda: Topic 4: Sample Exercise
1. Glossary
2. Standard offer
3. Additional environments
4. Sample exercise
5. Other considerations and recommendations
6. Checklist and resources
26
Agenda:
Create the environments plan in the beginning of the implementation
27
Context: Medium complexity project
28
Sample Exercise – Step 1
Sample Exercise – Step 2
Sample Exercise – Step 3
Sample Exercise – Step 4
Agenda: Topic 5: Other Considerations
1. Glossary
2. Standard offer
3. Additional environments
4. Sample exercise
5. Other considerations and recommendations
6. Checklist and resources
33
Agenda:
Purchasing add-on environments
Identify SKU
➢Map add-ons to a SKU
➢Obtain the list of SKUs and a quote from your licensing service reseller (LSR)
Define budget
➢Use the quote from the LSR for the identified SKU
➢Use the usage information as identified in the environment plan
Place order
➢Place an order with LSR for the identified SKU and quantity
➢LSR will fulfill the order by adding SKUs to the EA
➢Add-ons appear in the customer’s Microsoft 365 admin portal and LCS
Deploy
➢The add-on can be configured from LCS
Work closely with
your CSP or
Licensing Reseller
34
Common Data Service Add-Ons
• Common Data Service for Apps Database Capacity
• Common Data Service for Apps File Capacity
• Common Data Service for Apps Log Capacity
Multiple environments or
tenants
Create and manage
environments
Storage Capacity for the CDS
Capacity Add-Ons for the CDS
35
DO’s and DON’Ts for Finance and Operations Environments
DO’s
✓ Plan to use the Standard Acceptance Test
environment
✓ Deploy using an unnamed/service
account
✓ Assign an owner to environments
✓ Configure notifications for LCS users
✓ Deploy one Tier-1 for each developer
DON’Ts
Allocate multiple developers to a single
environment
Plan to use PROD as a non-production
environment
Plan to use a CHE for performance testing
or UAT
Provide all LCS users access to manage
environments
Go-Live on a Sandbox or Development
environment36
DO’s and DON’Ts for CDS Environments
DO’s
✓ Create separate environments for
Dev, Test, and Prod
✓ Define the purpose and mapping
between each CDS and F&O
environment
✓ Rename the default environment
DON’Ts
Use a single CDS for all activities
Create a database in an
environment unless there is a need
for the database
Allow all users to create new
environments
37
General DO’s and DON’Ts for Environment Planning
DO’s
✓ Plan environments early, and
schedule recurring review
✓ Define a naming standard
✓ Define security and governance for
your environments
✓ Plan your environment update
schedule
DON’Ts
Create a plan at the beginning and
then never review again
Deploy CDS and F&O in different
geos
Deploy DEV/TEST in different geos
than PROD
38
After the environment planning
Environment planning and Application Lifecycle Management (ALM)
39
Sample Environment Flow
Co
de a
nd
Data
Pro
mo
tio
n
F&O
PROD
Proj Ops
/ HR
PROD
CDS
PROD
CE Apps PROD
Proj Ops / HR
PROD
Power App/
Automate PROD
F&O
TEST
Proj Ops
/ HR
TEST
CDS
TEST
CE Apps TEST
Proj Ops TEST or
HR SANDBOX
Power App/
Automate TEST
F&O
DEV-n
Proj Ops
DEV-n
CDS
DEV-n
CE Apps DEV
40
Proj Ops DEV
Power App/
Automate DEV
Agenda: Topic 6: Checklist and Resources
1. Glossary
2. Standard offer
3. Additional environments
4. Sample exercise
5. Other considerations and recommendations
6. Checklist and resources
41
Agenda:
Use and adjust this baseline checklist
42
Additional Resources
Look at the following resources to go further:Trust Center
Terms and conditions of Microsoft services
Service Level Agreement
Dynamics 365 Finance and Supply Chain Management Service Description
Microsoft Dynamics 365 Licensing Guide
Infrastructure and availability
About the tenant, the subscriptions, the user accounts, etc.
Power Platform environment overview
Dual-write home page
TechTalk: Prospect to cash in Dual-write
TechTalk: Dual-write framework
TechTalk: Customer Engagement Application Lifecycle Management 43
Thank you!
44
