Skip to content

PL-600 architecture rules ​

The rules below turn product choices into one-line decisions. Start with the first principle: pick the lowest-code, most native, most supportable option that meets the constraint.


Architect First Principle ​

PL-600 is less about "can this tool do it?" and more about "is this the best architecture recommendation?"

Scenario SignalArchitect Move
Business outcome or success metricConvert to measurable success criteria and requirements traceability
Existing system owns the dataDecide connect vs import vs migrate based on latency, ownership, volume, and reporting need
External audienceDecide identity, licensing, surface, and row access before app type
Integration failure riskPick the component by delivery semantics: sync, async, durable, streaming, batch
Go-live issueGather evidence and isolate root cause before changing architecture
Multiple plausible toolsPick the lowest-code, most native, most supportable option that satisfies the constraint

Fast mental loop:

  1. Who uses it?
  2. Where does the data live and who owns it?
  3. What security boundary is required?
  4. Is the work interactive, background, batch, or event-driven?
  5. Is the goal implementation, architecture, or discovery?

ENVISION Fundamentals ​

Requirement Classification ​

If The Requirement Says...Classify As
"The system must let users create, approve, send, track, submit, view, update"Functional
"Within 3 seconds", "99.9% availability", "10,000 users", "retain for 7 years", "data must stay in region"Non-functional
"Support offline capture"Usually functional, unless the wording tests reliability/availability quality
"Be easy to use", "accessible", "secure", "scalable", "recoverable"Non-functional

Drill: do not let a number trick you. Numbers often mark NFRs, but "store 3 documents per case" can still be functional if it describes a capability.

User Stories ​

Valid format: As a <role>, I want <capability>, so that <benefit>.

Missing PartWhat It Becomes
RoleRequirement stub
CapabilityVague objective
BenefitTask, not a user story

Value, Risk, And Discovery ​

SignalRule
High value + low effortQuick win
High value + high effortBig investment
Low value + high effortDefer or challenge scope
Budget/skills/time shortageResource risk
Market strategy, scope creep, sponsorshipBusiness risk
Vendor, regulation, environmental dependencyExternal risk
Sensitive data exposure or unauthorized accessSecurity risk
Group ideationWorkshop
Broad async stakeholder feedbackSurvey
Observe actual work and pain pointsJob shadowing or task mining
Existing event logProcess mining
Record user actionsTask mining

Success Criteria ​

Anchor on the requirement's measurable verb and noun.

Requirement ShapeSuccess Criterion Shape
"Workers can operate the app"Adoption/usage
"Process completes under N seconds"Performance
"Reduce case resolution time by X%"Service outcome
"Data must be retained N years"Compliance/retention

Fit/Gap And Product Selection ​

RequirementFirst Check
Case, inquiry, customer service processDynamics 365 Customer Service
On-site work orders / techniciansDynamics 365 Field Service
Sales pipeline / opportunity processDynamics 365 Sales
Project services from sale to deliveryDynamics 365 Project Operations
Marketing journeys, contact capture, bounce/delivery evidenceCustomer Insights - Journeys
Chatbot / conversational intakeCopilot Studio, with Omnichannel for live handoff
SMS if not native in scenarioISV, connector, or AppSource gap
SharePoint documents with signaturesKeep SharePoint integration; digital signature usually needs ISV/AppSource
Geospatial routing or mapsBing Maps/Azure Maps/industry accelerator; not chatbot/AI Builder by default
Existing vendor product likely solves gapAppSource/ISV review before custom build

Decision order:

  1. Use native Dynamics or Power Platform capability when it directly fits.
  2. Use AppSource/ISV if the gap is a common productized need.
  3. Extend with Power Platform/Azure if the gap is unique or integration-heavy.
  4. Custom code only when platform-native and ISV options do not satisfy the constraint.

External Surface Selection ​

Audience / NeedBest Surface
Internal employees using Dataverse business process dataModel-driven app
Internal employees needing custom branded/mobile/device UXCanvas app
Internal users on D365 first-party processD365 app or Power Apps mobile
External customers/partners/contractors needing Dataverse-backed self-servicePower Pages
Invited collaborators around Microsoft 365 contentTeams plus SharePoint/Dataverse integration when the scenario points there
External users needing a canvas appOnly when licensing/identity supports it; otherwise suspect Power Pages
Customer chatCopilot Studio plus Omnichannel when live-agent handoff is needed

Repeat drill: contractors/partners/customers + Dataverse + no Power Apps licenses = Power Pages.

Power Pages security decomposition:

RequirementComponent
Permission containerWeb role
Row/table operationsTable permission
Anonymous or authenticated page accessWebpage access control
Invitation-only registration / auth behaviorSite settings / identity provider setup
Preferred portal languageContact/profile preference
Reusable portal codeWeb template
Reusable portal file assetWeb file
Small reusable content textContent snippet
Record collection or availability displayList/View
Single-record create/edit/displayBasic form
Guided multi-page entryMultistep form

Dataverse Modeling ​

Relationship Cardinality ​

RequirementPick
One parent has many children; each child has one parent1:N from parent to child
Each side can link to many of the other side with no natural owner rowN:N
Need metadata about the associationIntersect/custom table, not simple N:N
Parent delete should be blocked if children existReferential, Restrict Delete
Parent and child should not affect each other on deleteReferential, Remove Link
Child lifecycle follows parentParental/cascade behavior

Repeat drill: many records can reference one country = country table plus lookup, not N:N and not a choice.

Reference Data ​

Use A Reference Table + Lookup When...Use Choice/Choices When...
Values are reused across tables/appsValues are small and table-local
Values need metadata, localization, ownership, security, or admin lifecycleValues rarely change
Users search/filter/report by the valueNo extra columns are needed
Existing systems supply stable identifiersNo external mapping is required

External Data ​

RequirementComponent
Need data in Dataverse for app logic/reportingImport/migrate/dataflow
Need to show external rows without copyingVirtual table when provider supports it
Need scheduled transformed load into DataversePower Apps dataflow
Need analytics replication to lake/warehouseSynapse Link or analytical dataflow, by destination
External ID drives no-duplicate syncAlternate key plus Upsert

Connector Modernization ​

Use the Microsoft Dataverse connector for Dataverse-backed Dynamics 365 row operations. Treat older Dynamics 365/Common Data Service connector labels as legacy distractors unless the options force legacy wording.


Dataverse Security ​

NeedMechanism
Hierarchical org data isolationBusiness units plus role depth
Cross-region or sibling access without widening user role depthOwner team or sharing where the records live
Dynamic per-record temporary accessAccess team template
High-churn role assignmentMicrosoft Entra group team / Dataverse team
Column-level sensitive dataField security profile
External portal row/table accessPower Pages table permissions plus web roles
Environment membership segmentationMicrosoft Entra security group on environment
Cross-tenant guest access to DataverseB2B guest plus team/security-role model

Append / Append To ​

Use this exact wording until it is automatic:

PrivilegeMeaning
AppendThis row can be attached to another row
Append ToOther rows can be attached to this row

Examples:

ScenarioNeeded Privileges
Add a child/contact/note/activity to an accountAppend on the child row type, Append To on account
Associate a record to a lookup parentAppend on the associating row, Append To on the referenced parent

Repeat drill: lookup association needs Append on the child/associating row and Append To on the parent/referenced row.


Power Pages Boundaries ​

If The Page Needs...Use
A collection of records, availability rows, schedule-like displayList/View
One row entry or editBasic form
A guided process across pagesMultistep form
Reusable HTML/Liquid/custom portal logicWeb template
Reusable static assetWeb file
Reusable small text/contentContent snippet
Environment-specific values such as API URLSite setting
User authorizationWeb role plus table permissions

Integration Delivery Guarantees ​

The answer is often hidden in the guarantee, not the technology brand.

Requirement ShapePick
Wrap third-party REST API for use by Power Apps/flowsCustom connector
Synchronous business transaction logic inside DataversePlug-in or real-time workflow, depending option set
Lightweight outbound HTTP notificationWebhook
Durable buffering when receiver is slow/unavailableService Bus queue
Cloud-to-on-prem request/response with retry pathAzure Relay
High-volume telemetry streamingEvent Hubs
Dataverse to data lake/warehouse analyticsSynapse Link
Scheduled import/transform into DataverseDataflow
On-prem data source accessOn-premises data gateway
Legacy GUI-only automationDesktop flow/RPA
Event-driven API-capable automationAutomated cloud flow
Human-triggered one-off actionInstant cloud flow
User-guided stage processBusiness process flow

ALM, Migration, And Go-Live ​

ALM Sequence ​

StageRule
Initial source-control setupProject/repo, Build Tools, export pipeline, run
DevelopmentUnmanaged solution in dev
Test/UAT/prodManaged solution
Component version trackingSolution Packager or pac solution unpack/pack
Mixed assets plus data/custom codePackage Deployer
Environment-specific valuesEnvironment variables and connection references
Identity for pipelinesService principal/application user pattern

Migration ​

Requirement / FailureFirst Check
Preserve reference-data GUIDsConfiguration Migration Tool or import with GUID mapping
Lookup failuresParent tables loaded first
Duplicate/external ID issuesAlternate key plus upsert
Failed rows in one-shot importImport Data Wizard error export / import job details
Ongoing transformed importDataflow refresh history and row errors
Custom code creates duplicate side effectsDisable or adjust workflows/plug-ins/auditing/duplicate detection before load
Users missing from pickerEnvironment security group / provisioning issue before security-role tuning

Repeat drill: migration root cause before rerun. Do not increase batch size or reimport blindly.

Go-Live Diagnostics ​

SymptomFirst Suspect
Portal save is slowSynchronous plug-in or real-time logic in the transaction path
Canvas app startup is slowOnStart, too many columns/rows, sequential loading, missing Concurrent where useful
One canvas screen is slowThat screen's OnVisible and data calls
Flow delayed or failing under volumeService protection limit / per-user short-window throttling
Need flow-level failure detailFlow run history
Need Dataverse plug-in failure tracePlug-in trace log and SDK message processing steps
Need data-change historyAuditing history
Need aggregate platform healthPower Platform admin center analytics

Case-Study Decomposition ​

Case studies punish answer-first behavior. Use this grid before selecting anything.

LayerAsk
AudienceInternal, external, guest, customer, partner, contractor?
SurfaceModel-driven, canvas, Power Pages, Teams, D365 app, Copilot Studio?
DataDataverse, SharePoint, external system, lake/warehouse, document store?
SecurityBU/team/role, field security, Power Pages table permissions, Entra group, B2B/B2C?
AutomationCloud flow, desktop flow, BPF, plug-in, real-time workflow, child flow?
IntegrationConnector, custom connector, webhook, Relay, Service Bus, Synapse Link, dataflow?
ImplementationALM, migration, testing, limits, performance, readiness?

Personal study notes written from official documentation. Not affiliated with Microsoft or GitHub. Contains no exam questions.