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 Signal | Architect Move |
|---|---|
| Business outcome or success metric | Convert to measurable success criteria and requirements traceability |
| Existing system owns the data | Decide connect vs import vs migrate based on latency, ownership, volume, and reporting need |
| External audience | Decide identity, licensing, surface, and row access before app type |
| Integration failure risk | Pick the component by delivery semantics: sync, async, durable, streaming, batch |
| Go-live issue | Gather evidence and isolate root cause before changing architecture |
| Multiple plausible tools | Pick the lowest-code, most native, most supportable option that satisfies the constraint |
Fast mental loop:
- Who uses it?
- Where does the data live and who owns it?
- What security boundary is required?
- Is the work interactive, background, batch, or event-driven?
- 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 Part | What It Becomes |
|---|---|
| Role | Requirement stub |
| Capability | Vague objective |
| Benefit | Task, not a user story |
Value, Risk, And Discovery
| Signal | Rule |
|---|---|
| High value + low effort | Quick win |
| High value + high effort | Big investment |
| Low value + high effort | Defer or challenge scope |
| Budget/skills/time shortage | Resource risk |
| Market strategy, scope creep, sponsorship | Business risk |
| Vendor, regulation, environmental dependency | External risk |
| Sensitive data exposure or unauthorized access | Security risk |
| Group ideation | Workshop |
| Broad async stakeholder feedback | Survey |
| Observe actual work and pain points | Job shadowing or task mining |
| Existing event log | Process mining |
| Record user actions | Task mining |
Success Criteria
Anchor on the requirement's measurable verb and noun.
| Requirement Shape | Success 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
| Requirement | First Check |
|---|---|
| Case, inquiry, customer service process | Dynamics 365 Customer Service |
| On-site work orders / technicians | Dynamics 365 Field Service |
| Sales pipeline / opportunity process | Dynamics 365 Sales |
| Project services from sale to delivery | Dynamics 365 Project Operations |
| Marketing journeys, contact capture, bounce/delivery evidence | Customer Insights - Journeys |
| Chatbot / conversational intake | Copilot Studio, with Omnichannel for live handoff |
| SMS if not native in scenario | ISV, connector, or AppSource gap |
| SharePoint documents with signatures | Keep SharePoint integration; digital signature usually needs ISV/AppSource |
| Geospatial routing or maps | Bing Maps/Azure Maps/industry accelerator; not chatbot/AI Builder by default |
| Existing vendor product likely solves gap | AppSource/ISV review before custom build |
Decision order:
- Use native Dynamics or Power Platform capability when it directly fits.
- Use AppSource/ISV if the gap is a common productized need.
- Extend with Power Platform/Azure if the gap is unique or integration-heavy.
- Custom code only when platform-native and ISV options do not satisfy the constraint.
External Surface Selection
| Audience / Need | Best Surface |
|---|---|
| Internal employees using Dataverse business process data | Model-driven app |
| Internal employees needing custom branded/mobile/device UX | Canvas app |
| Internal users on D365 first-party process | D365 app or Power Apps mobile |
| External customers/partners/contractors needing Dataverse-backed self-service | Power Pages |
| Invited collaborators around Microsoft 365 content | Teams plus SharePoint/Dataverse integration when the scenario points there |
| External users needing a canvas app | Only when licensing/identity supports it; otherwise suspect Power Pages |
| Customer chat | Copilot 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:
| Requirement | Component |
|---|---|
| Permission container | Web role |
| Row/table operations | Table permission |
| Anonymous or authenticated page access | Webpage access control |
| Invitation-only registration / auth behavior | Site settings / identity provider setup |
| Preferred portal language | Contact/profile preference |
| Reusable portal code | Web template |
| Reusable portal file asset | Web file |
| Small reusable content text | Content snippet |
| Record collection or availability display | List/View |
| Single-record create/edit/display | Basic form |
| Guided multi-page entry | Multistep form |
Dataverse Modeling
Relationship Cardinality
| Requirement | Pick |
|---|---|
| One parent has many children; each child has one parent | 1:N from parent to child |
| Each side can link to many of the other side with no natural owner row | N:N |
| Need metadata about the association | Intersect/custom table, not simple N:N |
| Parent delete should be blocked if children exist | Referential, Restrict Delete |
| Parent and child should not affect each other on delete | Referential, Remove Link |
| Child lifecycle follows parent | Parental/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/apps | Values are small and table-local |
| Values need metadata, localization, ownership, security, or admin lifecycle | Values rarely change |
| Users search/filter/report by the value | No extra columns are needed |
| Existing systems supply stable identifiers | No external mapping is required |
External Data
| Requirement | Component |
|---|---|
| Need data in Dataverse for app logic/reporting | Import/migrate/dataflow |
| Need to show external rows without copying | Virtual table when provider supports it |
| Need scheduled transformed load into Dataverse | Power Apps dataflow |
| Need analytics replication to lake/warehouse | Synapse Link or analytical dataflow, by destination |
| External ID drives no-duplicate sync | Alternate 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
| Need | Mechanism |
|---|---|
| Hierarchical org data isolation | Business units plus role depth |
| Cross-region or sibling access without widening user role depth | Owner team or sharing where the records live |
| Dynamic per-record temporary access | Access team template |
| High-churn role assignment | Microsoft Entra group team / Dataverse team |
| Column-level sensitive data | Field security profile |
| External portal row/table access | Power Pages table permissions plus web roles |
| Environment membership segmentation | Microsoft Entra security group on environment |
| Cross-tenant guest access to Dataverse | B2B guest plus team/security-role model |
Append / Append To
Use this exact wording until it is automatic:
| Privilege | Meaning |
|---|---|
| Append | This row can be attached to another row |
| Append To | Other rows can be attached to this row |
Examples:
| Scenario | Needed Privileges |
|---|---|
| Add a child/contact/note/activity to an account | Append on the child row type, Append To on account |
| Associate a record to a lookup parent | Append 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 display | List/View |
| One row entry or edit | Basic form |
| A guided process across pages | Multistep form |
| Reusable HTML/Liquid/custom portal logic | Web template |
| Reusable static asset | Web file |
| Reusable small text/content | Content snippet |
| Environment-specific values such as API URL | Site setting |
| User authorization | Web role plus table permissions |
Integration Delivery Guarantees
The answer is often hidden in the guarantee, not the technology brand.
| Requirement Shape | Pick |
|---|---|
| Wrap third-party REST API for use by Power Apps/flows | Custom connector |
| Synchronous business transaction logic inside Dataverse | Plug-in or real-time workflow, depending option set |
| Lightweight outbound HTTP notification | Webhook |
| Durable buffering when receiver is slow/unavailable | Service Bus queue |
| Cloud-to-on-prem request/response with retry path | Azure Relay |
| High-volume telemetry streaming | Event Hubs |
| Dataverse to data lake/warehouse analytics | Synapse Link |
| Scheduled import/transform into Dataverse | Dataflow |
| On-prem data source access | On-premises data gateway |
| Legacy GUI-only automation | Desktop flow/RPA |
| Event-driven API-capable automation | Automated cloud flow |
| Human-triggered one-off action | Instant cloud flow |
| User-guided stage process | Business process flow |
ALM, Migration, And Go-Live
ALM Sequence
| Stage | Rule |
|---|---|
| Initial source-control setup | Project/repo, Build Tools, export pipeline, run |
| Development | Unmanaged solution in dev |
| Test/UAT/prod | Managed solution |
| Component version tracking | Solution Packager or pac solution unpack/pack |
| Mixed assets plus data/custom code | Package Deployer |
| Environment-specific values | Environment variables and connection references |
| Identity for pipelines | Service principal/application user pattern |
Migration
| Requirement / Failure | First Check |
|---|---|
| Preserve reference-data GUIDs | Configuration Migration Tool or import with GUID mapping |
| Lookup failures | Parent tables loaded first |
| Duplicate/external ID issues | Alternate key plus upsert |
| Failed rows in one-shot import | Import Data Wizard error export / import job details |
| Ongoing transformed import | Dataflow refresh history and row errors |
| Custom code creates duplicate side effects | Disable or adjust workflows/plug-ins/auditing/duplicate detection before load |
| Users missing from picker | Environment 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
| Symptom | First Suspect |
|---|---|
| Portal save is slow | Synchronous plug-in or real-time logic in the transaction path |
| Canvas app startup is slow | OnStart, too many columns/rows, sequential loading, missing Concurrent where useful |
| One canvas screen is slow | That screen's OnVisible and data calls |
| Flow delayed or failing under volume | Service protection limit / per-user short-window throttling |
| Need flow-level failure detail | Flow run history |
| Need Dataverse plug-in failure trace | Plug-in trace log and SDK message processing steps |
| Need data-change history | Auditing history |
| Need aggregate platform health | Power Platform admin center analytics |
Case-Study Decomposition
Case studies punish answer-first behavior. Use this grid before selecting anything.
| Layer | Ask |
|---|---|
| Audience | Internal, external, guest, customer, partner, contractor? |
| Surface | Model-driven, canvas, Power Pages, Teams, D365 app, Copilot Studio? |
| Data | Dataverse, SharePoint, external system, lake/warehouse, document store? |
| Security | BU/team/role, field security, Power Pages table permissions, Entra group, B2B/B2C? |
| Automation | Cloud flow, desktop flow, BPF, plug-in, real-time workflow, child flow? |
| Integration | Connector, custom connector, webhook, Relay, Service Bus, Synapse Link, dataflow? |
| Implementation | ALM, migration, testing, limits, performance, readiness? |