Dynamics 365 for Finance and Operations | Environment

Version 1.0.
Last modification 2018.01.31

About this sample:

This environment planning sample is delivered as-is.
It is intented to be used as material for training purposes as part of the Implementation Lifecycle

For more information, refer to the Environment

Walkthrough to build the environment planning:

- Step 1: Define the milestones in the timeline based on the project plan
- Step 2: Add the activities that require a supporting environment (e.g. develop customizations o
- Step 3: Determine the deployment option and topology to be used for the environments and tr
- Step 4: Build the environment plan out of the exercise to list what environments will be require

Definitions and acronyms:

Deployment option For Tier-1 environments, defines where the environment is hosted (se
Environment topology Defines the composition of the environment to be used (for example D
Licensing Defines how the environment is licensed and billed (see the terms EA
T1, T2, …, T5 Defines the Tier (type / Microsoft SKU) of the environment (Tier-1, Tie
Add-on An Add-on environment is an additional environment purchased by th
Standard A Standard environment is an environment comprised in the standard
Cloud-Hosted A Cloud-Hosted environment is an environment managed under the c
VHD A VHD environment is a environment hosted on-premises through the
EA An Enterprise Agreement (EA) defines the Microsoft products purcha
MPSA A MPSA (Microsoft Product Service Agreement) can be defined on to
CSP A Cloud Service Provider (CSP) contract defines the Microsoft produc
 | Environment Planning Sample

Implementation Lifecycle Workshop (session D1010 - Environment Planning).

refer to the Environment Planning Tech Talk

n
develop customizations or track configuration) throughout the implementation
r the environments and try to mutualize the environments
vironments will be required during the implementation and after

environment is hosted (see the terms Standard/Add-on, Cloud-Hosted or VHD)

to be used (for example Demo, Develop, Build and Test, Standard Acceptance Test, etc.)
d billed (see the terms EA, MPSA, CSP), see this link for more information
e environment (Tier-1, Tier-2, etc.)
ronment purchased by the customer and hosted under the Microsoft Azure subscription
omprised in the standard offer and hosted under the Microsoft Azure subscription
ent managed under the customer or partner Azure subscription
on-premises through the use of the VHDs downloadable from LCS
Microsoft products purchased by a customer
ent) can be defined on top of an EA to subscribe to Add-on environments on a monthly basis
ines the Microsoft products purchased through a Cloud Service Provider partner
 X Project activities
G Go-Live

Month JANUARY FEBRUARY MARCH APRIL MAY JUNE JULY AUGUST

Week 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

Phase Activity I I A A A A A Dd Dd Dd Dd Dd T T T T T T D D D D G S S S S
AUGUST SEPTEMBER OCTOBER NOVEMBER DECEMBER
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
 X Project activities
G Go-Live

Month JANUARY FEBRUARY MARCH APRIL MAY JUNE JULY

Week 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Phase Activity I I A A A A A Dd Dd Dd Dd Dd T T T T T T D D D D G S S S S
 AUGUST SEPTEMBER OCTOBER NOVEMBER DECEMBER
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
 X Project activities
G Go-Live
Environment type = Standard or Add-on (AO)
Environment type = Cloud-Hosted (C-H)
Environment type = VHD
PRODUCTION

Month JANUARY FEBRUARY MARCH APRIL

Week 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

Phase Activity Environment deployment & topology Environment ID I I A A A A A Dd Dd Dd Dd Dd T T T T T T

 MAY JUNE JULY AUGUST SEPTEMBER OCTOBER NOVEMBER DECEMBER
19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53

D D D D G S S S S
 ENVIRONMENT PLANNING (sample)

Environment ID Purpose

CLI-TEST Deliver initial training and perform process / integration testing

CLI-CONFIG Track the configuration

CLI-BUILD Generate builds and run automated tests

CLI-DATA Execute data migration activities

CLI-DEV1 Develop customizations

CLI-DEV2 Develop customizations

CLI-DEV3 Develop customizations

CLI-DEV4 Develop customizations

CLI-UAT Perform the User Acceptance Test and deliver the final training

CLI-PERF Perform the performance testing

PROD Operate the business

Deployment option Topology Owner

Standard Tier-2 / Standard Acceptance Test Project Manager (partner)

Cloud-Hosted Tier-1 / Demo Project Manager (partner)

Standard Tier-1 / Build and Test Project Manager (partner)

VHD Tier-1 / Develop and Test Data migration lead

Cloud-Hosted Tier-1 / Develop and Test Developer 1

Cloud-Hosted Tier-1 / Develop and Test Developer 2

Cloud-Hosted Tier-1 / Develop and Test Developer 3

Cloud-Hosted Tier-1 / Develop and Test Developer 4

Addon Tier-2 / Standard Acceptance Test Project Manager (customer)

Addon Tier-4 / Standard Performance Test Project Manager (partner)

Addon N/A IT manager (customer)

 Licensing To be ready by
To be maintained post Go-Live?
(EA/MPSA/CSP) Week

EA 2 Yes, to support PRODUCTION post Go-Live

Azure 3 No

EA 3 Yes, to patch PRODUCTION

N/A 3 No

Azure 8 Yes, to enrich the solution

Azure 8 Yes, to enrich the solution

Azure 8 No

Azure 8 No

MPSA 16 Yes, to test/validate new releases

MPSA 16 No

EA 21 N/A