ASD-DSD Architecture
...
2.3 Licensing Considerations.
3. Cloud Services Provisioning Guidelines & Best practices.
3.1 Power Platform application development is back ended by CDS.
...
All the resources in a group should share the same lifecycle - deploy, update, and delete them together.
Each resource can only exist in one resource group; however, a resource can move from one resource group to another group.
Can add or remove a resource to a resource group at any time.
A resource group can contain resources that are located in different regions.
A resource group can be used to scope access control for administrative actions.
A resource can interact with resources in other resource groups. This interaction is common when the two resources are related but don't share the same lifecycle (for example, web apps connecting to a database).
When creating a resource group, need to provide a location for that resource group. For compliance reasons, may need to ensure that data is stored in a particular region.
...
Refer to Annex A – Resources, Azure Provisioning Guidelines
...
This is summarized as follows:
Business Units
A business unit basically is a group of users. Large organizations with multiple customer bases often use multiple business units to control data access and define security roles so that users can access records only in their own business unit.
...
A solution is a container that encompasses Dynamics 365 CRM components.
A publisher is associated to a Solution, and is used to identify the prefix that will be used for any new entities that are created in the Solution.
ba. Would have a common Solution for ASD, which would contain entities that are potentially useful to multiple applications in ASD.
i. Any entities that would be created in this Solution would have a prefix of “asd_”
cb. Each project would then have their own solution which would identify a Publisher with a specific prefix. For example:
...
Deploy & Support considering the following:
ivi) Requires at a minimum an Authority to Operate (ATO), a Security ConOps, an SOS and a LOA to provide to security for review. Security will then provide a SRTM to be populated and to fulfil security considerations;
vii) Furthermore a PPIA w/ ATIP; and architecture views to describe the solution (business, application, data, and infrastructure) may be called upon throughout the ATO process.
viiii) Depending on the nature and complexity of the solution, a more comprehensive review & approval process may be instilled on the project; e.g. full ARB (architecture review board) process.
...
Gatekeeper | Overseer | Commentary (R&R, operational insight and the like) |
|
|
|
|
TBD | documented once the initial review has been completed.