01 · DYNAMICS UNIVERSE
Microsoft Dynamics 365 is not a product — it is an ecosystem.
27 components across five layers. Each with its own skill profile, hiring market, and relevance for our work.
06 · ALL COMPONENTS
All 27 components in detail.
Business Applications
End-customer modules for ERP, CRM, and Verticals
Core D365 Finance General Ledger, Group Accounting
§ 1 · What is it
The financial module from the F&SCM block (still widely known in the market as F&O or Finance & Operations). It covers general ledger, accounts receivable and payable, fixed asset accounting, consolidation, budgeting, and reporting. The historical lineage is Axapta, Dynamics AX, D365 Finance & Operations, D365 Finance & Supply Chain Management.
§ 2 · Where is it deployed
Enterprises and upper mid-market with complex group accounting, multiple legal entities, and regulatory depth (pharma, financial services, regulated industry). Implementations typically run over several years and multiple phases.
§ 3 · Which skills are involved
Functional: financial accounting, consolidation, tax, VAT logic, intercompany, Electronic Reporting, Lifecycle Services. Technical: X++, Data Management Framework, Power Platform integration via Dataverse, Azure DevOps for build and release.
§ 4 · Typical AlpineReach roles
Senior Finance Functional Consultant, Finance Solution Architect, Finance Lead in programme setups, Technical Consultant F&SCM (X++).
§ 5 · Hiring insight
Senior Finance Consultants with a genuine programme track record are scarce in DACH. Many are tied up in long-running rollouts and unavailable. Our search runs typically take six to twelve weeks depending on sector and language profile.
§ 6 · Typical confusion
Finance Consultant is not the same as Finance Solution Architect. Many profiles know booking logic but not programme architecture, integrations, and global template rollouts.
Core Supply Chain Management Production, Warehouse, MRP
§ 1 · What is it
Supply Chain Management is the operational half of the F&SCM block. It covers procurement, inventory management, production, warehousing, and transport. Many in the market still refer to it as F&O or SCM; in the official Microsoft licensing model it is a separate module that can be licensed alongside Finance or independently.
§ 2 · Where is it deployed
Manufacturing companies, trade with complex logistics, regulated industries requiring track-and-trace. Frequently in multi-tier production setups with plant and warehouse networking.
§ 3 · Which skills are involved
Functional: production control, MRP, Advanced Warehouse Management, Master Planning, EDI integrations. Technical: X++ for custom logic, Dataverse integration, Power Apps for mobile warehouse processes, IoT integrations via Azure.
§ 4 · Typical AlpineReach roles
Senior SCM Functional Consultant, SCM Solution Architect, Production or WMS Consultant, Technical Consultant F&SCM (X++) with SCM focus.
§ 5 · Hiring insight
Functional SCM profiles with genuine production depth are rarer than pure Finance profiles. Anyone who truly knows Master Planning has virtually free choice of mandates in DACH.
§ 6 · Typical confusion
WMS Consultant is not the same as SCM Consultant. Many bring warehouse process experience without the broader Master Planning context.
Core Business Central Mid-Market ERP, AL
§ 1 · What is it
Business Central is the cloud evolution of Dynamics NAV (formerly Navision). It covers financial accounting, sales, purchasing, inventory, and basic production. Customisation is done via the AL (Application Language), and extensions are installed via AppSource or directly in the tenant.
§ 2 · Where is it deployed
Mid-market companies with twenty to five hundred employees, typically in manufacturing, trade, and services. Implementations are significantly shorter than F&SCM, often three to nine months.
§ 3 · Which skills are involved
Functional: BC module knowledge, local accounting standards (Swiss GAAP FER, HGB, RLG), Swiss, German, and Austrian localisations. Technical: AL development, extensions, Power Platform integration, REST API integration.
§ 4 · Typical AlpineReach roles
Senior Business Central Functional Consultant, Business Central Developer (AL), Business Central Solution Architect, BC In-house Consultant.
§ 5 · Hiring insight
The Swiss market is shaped by a manageable number of specialised Microsoft partners. Senior profiles often move between the same three to five firms, which makes in-house transitions an attractive option.
§ 6 · Typical confusion
NAV experience is not the same as Business Central maturity. Many know the old on-premise world but not the modern extension model and cloud lifecycle logic.
Core Project Operations Project Business, Resources, Billing
§ 1 · What is it
Project Operations connects the sales side of a project (CE logic) with operational delivery and invoicing (F&SCM logic). It is the module for project-based organisations such as IT services firms, engineering consultancies, and construction companies. It exists in two variants: Core and Integrated with ERP.
§ 2 · Where is it deployed
Project-driven industries with a mix of T&M and fixed-price engagements. Frequently in setups where Sales, Resource Management, and Finance must work more closely together than in classic ERP implementations.
§ 3 · Which skills are involved
Functional: Project Operations configuration, resource scheduling, WIP and revenue recognition, integration between CE and F&SCM worlds. Technical: Dataverse, Power Automate for approval flows, plug-ins, and optionally X++ when the Finance backend is involved.
§ 4 · Typical AlpineReach roles
Project Operations Consultant, PO Solution Architect, hybrid F&SCM and CE profiles.
§ 5 · Hiring insight
Profiles who genuinely bring Project Operations, Dataverse, and the Finance backend together in production are very rare in DACH. In practice, shortlists almost always emerge from network and referrals rather than active search.
§ 6 · Typical confusion
CE Sales Consultants often have no project invoicing knowledge, while F&SCM profiles rarely have resource scheduling depth. True hybrids are the exception.
Core D365 Sales B2B Sales CRM
§ 1 · What is it
Sales is the classic sales CRM from the Customer Engagement family. It covers leads, opportunities, quotes, orders, forecasting, and sales pipeline management. It is the direct successor to Microsoft Dynamics CRM.
§ 2 · Where is it deployed
B2B sales organisations with complex sales cycles, frequently combined with Customer Insights for marketing automation and Customer Service for the post-sales phase.
§ 3 · Which skills are involved
Functional: sales process design, forecasting, Sales Accelerator, lead scoring. Technical: Dataverse, Power Automate, plug-in development (.NET), JavaScript for client customisation.
§ 4 · Typical AlpineReach roles
Senior CE Functional Consultant, CE Solution Architect, Senior CE Developer.
§ 5 · Hiring insight
Pure Sales profiles are fairly standard in DACH. The interesting profiles are those who think Sales, Customer Service, and Customer Insights as one connected platform. Senior CE generalists of this kind are what our clients search for most.
§ 6 · Typical confusion
CRM Consultant is not the same as CE Architect. Many know the UI configuration but not the platform architecture across Sales, Service, and Insights.
Core Customer Service Cases, Omnichannel
§ 1 · What is it
Customer Service covers case management, knowledge bases, service level agreements, omnichannel contact (voice, chat, email), queue routing, and increasingly AI-assisted response suggestions. It shares data and platform with Sales and Marketing.
§ 2 · Where is it deployed
Customer care centres, B2B support, technical service organisations. Frequently in combination with Field Service when service extends beyond the phone to on-site visits.
§ 3 · Which skills are involved
Functional: case routing, SLA configuration, Omnichannel for Customer Service, Knowledge Management. Technical: Dataverse, Power Automate, Copilot Studio for bot integrations.
§ 4 · Typical AlpineReach roles
CE Functional Consultant with Service focus, Omnichannel Architect.
§ 5 · Hiring insight
Customer Service mandates are stable in DACH, but the skill market around Omnichannel and Copilot integration is shifting rapidly. Profiles who combine both stand out from the candidate pipeline.
§ 6 · Typical confusion
Service Desk is not the same as Customer Service. ITIL profiles often bring the wrong focus for customer-centric service mandates.
Adjacent Customer Insights Marketing Automation, Journeys
§ 1 · What is it
Customer Insights today consists of two components: Customer Insights - Data (the CDP component, formerly Customer Insights) and Customer Insights - Journeys (the marketing automation component, formerly D365 Marketing). Microsoft has merged both under one name; professionally they remain two very different skill profiles. In the market, profiles are still commonly referred to as Marketing Automation, CDP, or D365 Marketing.
§ 2 · Where is it deployed
Data side: Customer Data Platform projects, frequently in retail, insurance, banking. Journeys side: marketing automation for B2C and B2B, trigger-based campaigns, lead nurturing.
§ 3 · Which skills are involved
Data: data modelling, identity resolution, segmentation, integration with Fabric or ADF. Journeys: customer journey design, email templates, trigger strategy, compliance (GDPR, Swiss nFADP).
§ 4 · Typical AlpineReach roles
Customer Insights Specialist (Data or Journeys, rarely both), CE Architect with CI depth.
§ 5 · Hiring insight
The two worlds are merging unevenly. Few profiles master both. Clients often do not know which of the two sides they are actually looking for. I always clarify this early in the first conversation.
§ 6 · Typical confusion
CDP specialist is not the same as marketing automation expert. Even within a Microsoft stack the two worlds speak different languages.
Adjacent Field Service Field Operations, Scheduling
§ 1 · What is it
Field Service covers scheduling, route optimisation, spare parts management, technician apps, and asset management. It is tightly integrated with Customer Service and frequently uses IoT data from Azure for predictive maintenance.
§ 2 · Where is it deployed
Mechanical and plant engineering, lift and HVAC technology, telecommunications, energy and utility companies -- everything with field technicians.
§ 3 · Which skills are involved
Functional: Resource Scheduling Optimization, Inspections, Connected Field Service. Technical: mobile Power Apps for technicians, IoT integrations via Azure, map integration.
§ 4 · Typical AlpineReach roles
Field Service Functional Consultant, Field Service Architect, Integration Consultant for IoT connections.
§ 5 · Hiring insight
Field Service is a growing market in Swiss mechanical engineering. Profiles with genuine scheduling practice combined with the Microsoft stack are rare. We typically find them at specialised Microsoft partners rather than end customers.
§ 6 · Typical confusion
Scheduling experience from SAP or bespoke solutions transfers only partially. The D365 Field Service logic is its own discipline.
Adjacent D365 Commerce Retail, POS, Loyalty
§ 1 · What is it
Commerce is the retail module of the F&SCM family. It covers point-of-sale (POS), headquarters management, loyalty, eCommerce frontend, and omnichannel logic. It is the cloud evolution of the Retail extension for Dynamics AX.
§ 2 · Where is it deployed
Multi-store retailers with their own POS, vertical retailers (fashion, sports, specialty food), mixed D2C/B2B setups. Frequently combined with Customer Insights for the loyalty programme.
§ 3 · Which skills are involved
Functional: POS configuration, loyalty, channel logic, pricing. Technical: Commerce SDK, Retail Server, POS-level customisation, headless integrations.
§ 4 · Typical AlpineReach roles
Commerce Functional Consultant, Retail Solution Architect, POS Developer.
§ 5 · Hiring insight
Commerce mandates are rare in Switzerland, more regular in Germany, and exceptional in Austria. Anyone combining retail experience with Microsoft depth has a very clear market.
§ 6 · Typical confusion
eCommerce platform experience (Shopify, Salesforce Commerce Cloud) is not the same as D365 Commerce. POS depth cannot be derived from a web shop background.
Adjacent Human Resources HR on F&SCM Infrastructure
§ 1 · What is it
Human Resources is the HR module of D365. It was operated as a standalone product for a period and then brought back into the Finance-and-Operations infrastructure as part of the Infrastructure Merge. Many clients are still in migration or consolidation scenarios depending on their history.
§ 2 · Where is it deployed
Mid-market and enterprise organisations that want to keep HR master data, talent development, compensation and benefits on the same platform as their ERP. Payroll almost always runs via external specialist systems.
§ 3 · Which skills are involved
Functional: HR master data modelling, compensation plans, benefit programmes, integration with local payroll providers. Technical: Dataverse integration, Power Apps for self-service portals, secure data modelling for personnel data.
§ 4 · Typical AlpineReach roles
D365 HR Consultant, HR Architect with integration focus.
§ 5 · Hiring insight
HR specialists in the Microsoft environment are thin on the ground in DACH. Many come from SAP HCM or Workday and need to build Microsoft depth first. Career transitions only work for us when HR process depth is strong from the outset.
§ 6 · Typical confusion
SAP HCM experience transfers conceptually but not technically. Migration to D365 HR is non-trivial.
Low-Code & Process Automation
Platforms for Citizen Developers and professionals
Core Power Apps Canvas, Model-driven, Power Fx
§ 1 · What is it
Power Apps is the low-code platform of the Power Platform, with two worlds: Canvas Apps for free UI design on any data source, and Model-driven Apps for standard business applications on Dataverse. The formula language Power Fx is used in both.
§ 2 · Where is it deployed
In-house tools, self-service portals, mobile extensions to D365 modules, process apps for business units. Frequently as a bridge between D365 and legacy systems.
§ 3 · Which skills are involved
Power Fx, Canvas design, Model-driven customisation, Dataverse modelling, connector configuration, optionally pro-code plug-ins.
§ 4 · Typical AlpineReach roles
Power Platform Engineer, Power Apps Developer, Solution Architect Power Platform.
§ 5 · Hiring insight
Pure low-code profiles are plentiful in the market. Senior roles today almost always demand pro-code depth (C#, plug-ins, custom connectors, AI integration). This hybrid layer is one of the most sought-after skill combinations right now.
§ 6 · Typical confusion
Citizen Developer is not the same as Power Platform Engineer. Anyone who only clicks Canvas Apps together will fail at senior mandates.
Core Power Automate Cloud Flows, RPA
§ 1 · What is it
Power Automate executes workflows, both in the cloud (Cloud Flows) and on desktops via RPA (Desktop Flows). It is the central automation layer of the Power Platform and deeply integrated into almost every D365 module.
§ 2 · Where is it deployed
Approval workflows, data transport between systems, RPA automation for legacy systems without APIs, event-driven processes in CE and F&SCM.
§ 3 · Which skills are involved
Cloud flow design, trigger strategy, connector selection, error handling, optionally custom connectors via OpenAPI or Swagger, RPA for legacy integration.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role. Power Automate is a mandatory skill for Power Platform Engineers and CE Consultants. Increasingly relevant in F&SCM environments for approval, notification, and integration processes.
§ 5 · Hiring insight
Anyone who builds Power Automate cleanly rather than just clicking flows together is usually also strong in Power Apps and Dataverse. In our experience the three are inseparable.
§ 6 · Typical confusion
Flows are not architecture. Many profiles build workflows without a plan for error handling or scaling.
Niche Power Pages External Portals
§ 1 · What is it
Power Pages (formerly Power Apps Portals, before that Adxstudio) is the Power Platform component for external web portals. It is used when customers, suppliers, or partners need web access to Dataverse data.
§ 2 · Where is it deployed
Supplier portals, customer self-service, applicant portals, citizen portals in the public sector.
§ 3 · Which skills are involved
Liquid templating, portal security model, Dataverse configuration, HTML and CSS customisation, web standards.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role. Power Pages appears as a specialist skill in Power Platform Architect profiles.
§ 5 · Hiring insight
Power Pages specialists are rare and typically housed at Microsoft partners rather than end customers. Anyone with portal mandates should declare this early in the job brief.
§ 6 · Typical confusion
Web developer experience is not the same as Power Pages maturity. Liquid and the Dataverse security model are their own disciplines.
Data, Analytics & Customer Data
Data backbone, analytics, Customer Data Platform
Core Dataverse + CDM Data Backbone, Security
§ 1 · What is it
Dataverse is the database platform underlying Power Platform and Customer Engagement. It is based on the Common Data Model (CDM), a normalised collection of business entities designed to make data exchangeable between Microsoft apps and third-party providers.
§ 2 · Where is it deployed
Virtually every CE module, every Power App on standard business data, many Power Automate flows. F&SCM uses Dataverse via Dual-write as a bridge to Power Platform and Customer Insights.
§ 3 · Which skills are involved
Data modelling (tables, columns, relationships), security model (business units, teams, field-level security), plug-ins (.NET), optionally virtual tables for external data.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role. Dataverse is a mandatory skill for every Power Platform Engineer and CE Solution Architect.
§ 5 · Hiring insight
Dataverse security depth is the most common blind spot in candidate profiles. Anyone who truly masters the model (not just knows the standard roles) belongs to the rare top tier in any setup.
§ 6 · Typical confusion
Dataverse is not SQL Server. Anyone coming from classical relational modelling regularly underestimates the security model.
Core Dual-write F&SCM Dataverse Bridge
§ 1 · What is it
Dual-write is the bidirectional synchronisation layer between F&SCM (Finance, Supply Chain Management) and Dataverse. It ensures that master and transactional data stays consistent between the ERP and the CE/Power Platform world without building a separate integration architecture.
§ 2 · Where is it deployed
In virtually every mandate running F&SCM and Customer Engagement in parallel production. A mandatory component for Customer Insights - Data when F&SCM source data is involved.
§ 3 · Which skills are involved
Map configuration between F&SCM tables and Dataverse entities, conflict resolution, initial synchronisation strategy, understanding of the Lifecycle Services integration.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role. Dual-write depth is a skill add-on in F&SCM Solution Architect and Integration Specialist profiles.
§ 5 · Hiring insight
Dual-write is often underestimated in job briefs. Clients realise only during the project that map complexity demands its own profile. We see this regularly as a late-stage requirement.
§ 6 · Typical confusion
Dual-write is not the same as Data Integration Framework. The tools overlap but are conceptually different.
Core Power BI DAX, Reporting
§ 1 · What is it
Power BI is the reporting and visualisation layer in the Microsoft stack. Since Fabric it is technically part of it, but remains independently licensable. DAX is the modelling language; Power Query (M) handles data preparation.
§ 2 · Where is it deployed
Virtually every Microsoft data landscape. Frequently as the frontend on Fabric, Synapse, SQL Server, or directly on F&SCM and CE data via Dataverse.
§ 3 · Which skills are involved
DAX, Power Query (M), data modelling (star schema), row-level security, performance tuning, deployment pipelines.
§ 4 · Typical AlpineReach roles
Senior Power BI Developer, BI Lead, in combination with Fabric also Analytics Engineer.
§ 5 · Hiring insight
Power BI is the most common entry point into the Microsoft stack. But senior roles demand DAX depth plus data modelling maturity, which some candidates have and some do not. Our first-profile hit rate here is lower than in most other areas.
§ 6 · Typical confusion
Excel power user is not the same as BI Developer. DAX and modelling hygiene are their own discipline.
Adjacent Microsoft Fabric Lakehouse, OneLake
§ 1 · What is it
Microsoft Fabric is the SaaS analytics platform that since 2023 bundles the previously separate tools Data Factory, Synapse, Power BI, and several others into one Lakehouse-based stack. It modernises and unifies what previously required multiple licensing and architecture paths.
§ 2 · Where is it deployed
Data platform modernisations, greenfield analytics projects, consolidation of heterogeneous reporting landscapes. ADF and Synapse remain relevant in existing architectures.
§ 3 · Which skills are involved
Lakehouse modelling (Delta Lake), OneLake, notebooks (Python or Scala), pipelines, Direct Lake with Power BI, optionally Real-Time Intelligence.
§ 4 · Typical AlpineReach roles
Data Engineer with Microsoft stack, Analytics Architect, Senior BI Consultant with Fabric experience.
§ 5 · Hiring insight
The market is split: Senior data profiles with a classical ADF or Synapse background need to learn the Fabric modelling paradigm from scratch. Profiles with genuine production experience in Fabric are still thin on the ground in 2026; salary growth in this skill is strong.
§ 6 · Typical confusion
Fabric is not simply Power BI Premium plus Synapse. The Lakehouse logic is its own paradigm.
Adjacent Customer Insights - Data CDP Component
§ 1 · What is it
Customer Insights - Data is the Customer Data Platform component. It consolidates customer data from heterogeneous sources, resolves identities, builds segments, and makes them available to marketing, service, and sales applications.
§ 2 · Where is it deployed
CDP projects in retail, insurance, banking. Frequently combined with Fabric or ADF for data ingestion and with Customer Insights - Journeys for activation.
§ 3 · Which skills are involved
Data modelling, identity resolution, segmentation, integration with Fabric or ADF, compliance (GDPR, Swiss nFADP).
§ 4 · Typical AlpineReach roles
Customer Insights Specialist (Data focus), CDP Architect, hybrid profiles combining data engineering with marketing understanding.
§ 5 · Hiring insight
CDP specialists often come from the Salesforce or Tealium ecosystem and need to learn the Microsoft stack from scratch. Clients regularly underestimate the lead time required for data ingestion.
§ 6 · Typical confusion
CDP is not the same as a CRM database. Identity resolution and segment logic are their own craft.
AI, Copilot & Agents
AI layer across the D365 stack
Adjacent Copilot for D365 AI in the module, contextual
§ 1 · What is it
Copilot for Dynamics 365 is the AI layer embedded in almost every D365 module. It answers questions about business data, generates text, summarises records, and suggests actions. Technically it is built on Azure OpenAI plus module-specific data connections.
§ 2 · Where is it deployed
In every D365 module that has it licensed. Productivity gains in Service, Sales, Finance analysis, marketing copy.
§ 3 · Which skills are involved
Understanding of data models in the respective D365 modules, prompt design, optionally customisation via Copilot Studio, governance and compliance logic.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role. Copilot experience in 2026 is a valuable additional skill for CE and Power Platform Architects.
§ 5 · Hiring insight
Anyone who has properly configured Copilot in a production setup and built governance has a clear differentiator in 2026. Most profiles so far bring only demo or PoC experience.
§ 6 · Typical confusion
Copilot demos are not the same as Copilot in production. The gap from click-through demo to enterprise rollout is large.
Adjacent Azure OpenAI + AI Builder Pro-Code AI plus Low-Code AI
§ 1 · What is it
Azure OpenAI is the pro-code and enterprise AI layer. AI Builder is the low-code AI functionality within the Power Platform, partly connected to Azure OpenAI. Together they cover the two layers on which AI is built in the D365 environment: deeply integrated in code, and accessible in Power Apps or Power Automate.
§ 2 · Where is it deployed
Azure OpenAI: custom AI solutions above D365 out-of-box features, own agents, document processing, semantic search. AI Builder: form recognition, sentiment analysis, predictions in Power Platform solutions.
§ 3 · Which skills are involved
Azure OpenAI: prompt engineering, RAG architecture, embedding stores (typically Azure AI Search), latency and cost tuning, security architecture. AI Builder: model selection, integration with Power Apps and flows.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role in our mandates. Skill add-on for modern Solution Architects.
§ 5 · Hiring insight
Genuine production experience with Azure OpenAI in enterprise setups is still thin in 2026. More often we see profiles with consumer-grade OpenAI experience without depth in Azure governance.
§ 6 · Typical confusion
ChatGPT experience is not the same as Azure OpenAI architecture. Enterprise security, EU data residency, and cost tuning are separate requirements.
Adjacent Copilot Studio Conversational Agents
§ 1 · What is it
Copilot Studio (formerly Power Virtual Agents) is the low-code platform for building chatbots and AI agents. Today it is significantly more tightly connected to Azure OpenAI than in the PVA era. It is frequently used for internal knowledge agents and external service bots.
§ 2 · Where is it deployed
First-level support bots, internal HR and IT self-service agents, supplier enquiries, and increasingly complex agents with tool calls.
§ 3 · Which skills are involved
Topics, trigger phrases, generative actions, integration with Dataverse and third-party systems, prompt design, testing strategy.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role. Copilot Studio is a relevant skill in modern Power Platform Engineer and CE Architect profiles.
§ 5 · Hiring insight
The market for Copilot Studio specialists is very young. Profiles with genuine production experience are scarce. Anyone who accompanied first implementations in 2024 or 2025 is in demand today.
§ 6 · Typical confusion
PoC bots are not the same as production agents. Governance and testing requirements in enterprise setups are their own discipline.
Integration, Identity & Azure Foundation
Identity, integration, compute, data movement
Core Entra ID Identity
§ 1 · What is it
Entra ID (formerly Azure Active Directory) is the identity and access layer for all Microsoft cloud services, including D365 and Power Platform. Single sign-on, Conditional Access, multi-factor authentication, B2B and B2C scenarios.
§ 2 · Where is it deployed
In every D365 and Power Platform tenant. Heavily configured in more complex setups, particularly for B2B scenarios (partner access) and B2C (portal logins).
§ 3 · Which skills are involved
Conditional Access, app registration, OAuth flows, Identity Governance, B2B and B2C configuration.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role in D365 mandates. Entra ID depth is mandatory for every Solution Architect.
§ 5 · Hiring insight
Pure Entra ID profiles are at home in the Microsoft Security world, not the D365 world. In our mandates we expect the knowledge in the Solution Architect profile but do not search for it separately.
§ 6 · Typical confusion
On-premise AD experience is not the same as Entra ID maturity. Cloud identity concepts (Conditional Access, B2B) are their own disciplines.
Adjacent Logic Apps EAI Workflows
§ 1 · What is it
Logic Apps is the Azure-native workflow engine. It overlaps conceptually with Power Automate but is better suited for complex enterprise integrations with high throughput requirements, B2B standards (AS2, EDIFACT), and monitoring.
§ 2 · Where is it deployed
EAI scenarios between D365, third-party systems, and external partners. Frequently combined with Service Bus, API Management, and Functions.
§ 3 · Which skills are involved
Logic Apps Designer, ARM or Bicep deployment, B2B connector configuration, on-premise integration via Data Gateway.
§ 4 · Typical AlpineReach roles
Integration Specialist (more often at Microsoft partners), Solution Architect with integration focus.
§ 5 · Hiring insight
Logic Apps profiles tend to be more experienced and often come from the BizTalk world. The overlap with D365 functional knowledge is small, which is why we almost always place these profiles in architecture roles.
§ 6 · Typical confusion
Logic Apps is not the same as Power Automate. The choice between the two is an architecture decision, not a UX question.
Niche Service Bus Messaging
§ 1 · What is it
Microsoft's enterprise messaging platform. Topics, queues, subscriptions -- suited for decoupled integrations, event-driven architectures, and reliable messaging between microservices or between D365 and third-party systems.
§ 2 · Where is it deployed
Decoupled integration architectures, frequently in combination with Logic Apps or Functions. When a mandate mentions eventual consistency or high throughput, Service Bus is usually part of the answer.
§ 3 · Which skills are involved
Topic and queue design, subscription filters, dead-letter handling, sessions, premium tier configuration for high throughput.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role. Service Bus is specialist knowledge in the architect's toolkit.
§ 5 · Hiring insight
Service Bus rarely appears as a mandatory skill in client briefs but is frequently present in practice. Experienced architects have it in their repertoire without it appearing prominently on their CV.
§ 6 · Typical confusion
Queues are not the same as topics. The choice between the two has consequences for scaling and routing.
Adjacent Functions Serverless
§ 1 · What is it
Azure Functions is Microsoft's serverless compute platform. C# or Python for custom logic, triggers from Service Bus, HTTP, Timer, Event Grid, Dataverse events. It complements Power Automate where pro-code depth is needed.
§ 2 · Where is it deployed
Custom interfaces, API wrappers, batch jobs, event-driven logic between D365 and third-party systems.
§ 3 · Which skills are involved
C# (.NET) or Python, Function App architecture, deployment via Bicep or ARM, Application Insights for monitoring.
§ 4 · Typical AlpineReach roles
Rarely as a standalone role. Functions are standard in the architect and senior developer skill set.
§ 5 · Hiring insight
Functions have reached the point where any senior developer can handle them. True specialists barely exist; those who master this more deeply in an architectural sense tend to be pro-code Power Platform Engineers.
§ 6 · Typical confusion
Function Apps are not the same as microservices. Architectural discipline is its own layer above the technology.
Adjacent Data Factory Classic ETL
§ 1 · What is it
Azure Data Factory (ADF) is Microsoft's classic ETL engine. Pipelines, Data Flows, connection to on-premise sources via Self-Hosted Integration Runtime. Since Fabric it competes with Fabric Pipelines, but remains central in many existing architectures.
§ 2 · Where is it deployed
Existing data warehouse landscapes, ETL between D365 and data lake or Synapse, hybrid on-premise/cloud scenarios.
§ 3 · Which skills are involved
Pipeline design, Data Flows, mapping and wrangling logic, trigger strategies, Self-Hosted Integration Runtime, monitoring.
§ 4 · Typical AlpineReach roles
Data Engineer with Microsoft focus, BI or DWH Architect.
§ 5 · Hiring insight
ADF profiles with senior depth are well represented. The interesting angle is who has made the transition to Fabric and can bridge both worlds.
§ 6 · Typical confusion
ADF is not the same as SSIS. Cloud ETL brings its own concepts (Integration Runtimes, Mapping Data Flows, trigger strategies).
Niche Synapse Enterprise DWH, Pre-Fabric
§ 1 · What is it
Azure Synapse Analytics is Microsoft's integrated analytics platform combining SQL-based data warehousing with Spark for big data processing. Since Fabric, new projects predominantly start there; Synapse remains relevant in existing architectures and as a specialist platform.
§ 2 · Where is it deployed
Existing enterprise data warehouses, large-scale analytics on D365 data, setups where Synapse Link for Dataverse exports data directly.
§ 3 · Which skills are involved
Synapse SQL (dedicated and serverless pools), Spark (Python or Scala), pipeline design, Synapse Link configuration, integration with Power BI.
§ 4 · Typical AlpineReach roles
Data Engineer with Microsoft stack, DWH Architect in brownfield setups.
§ 5 · Hiring insight
Synapse mandates are becoming rarer as Fabric absorbs the new project share. Profiles with Synapse depth are often experienced data engineers who are now learning Fabric in parallel.
§ 6 · Typical confusion
Synapse is not the same as Synapse Link. The first is a data platform; the second is a specific export feature from Dataverse and D365.
07 · NEXT STEP
This map shows the terrain. The roles on it we prefer to discuss directly.
We are specialised exclusively in Microsoft Dynamics 365 — across all five layers. If you are looking for senior profiles in this ecosystem, get in touch.
Let's talk