You read:
How to build Partner Relationship Management on Microsoft Dynamics 365: architecture, options, ISVs
As your partner ecosystem grows, it becomes important to have a more organised way of handling Partner Relationship Management.
Dynamics 365 provides a strong foundation, but PRM processes often go beyond the capabilities of standard CRM. These include Partner Acquisition, Partner Onboarding, Channel Marketing, MDF management, Co-Selling, Deal Registration, and partner-driven after-sales support.
This means that every organisation working on Microsoft Dynamics 365 needs to define the right level of PRM process integration and decide which approach makes the most sense for their specific situation.
PRM in Dynamics 365 and Power Platform
The optimal PRM architecture depends primarily on three factors:
- Relationship between the partner channel and direct sales teams: If partner sales operates in parallel to direct sales, it becomes essential to integrate data and information between these channels to avoid conflicts and cannibalisation. The larger these channels grow, the deeper the integration of data, processes, and customer-related documentation needs to be.
- Complexity and size of the partner channel: Up to a certain scale of the partner network (typically 10–15 partners for non-complex processes), it is possible to manage the channel without specialised tools. As the channel grows or processes become more complex, it is important to plan for scalable solutions, including integrations with CRM, BI tools, ERP systems, process automation, and—where needed—a solid Partner Portal.
- Internal competencies in Dynamics 365 and the Power Platform: When operating on Microsoft Dynamics 365 and extending it to support PRM processes, adoption and time-to-value improve significantly if the PRM solution allows self-configuration. While more complex integrations can be handled with external support, enabling in-house teams to manage minor configurations greatly increases PRM team efficiency.
Three approaches to PRM in the Dynamics ecosystem
1. Integrating a dedicated external PRM platform (stand-alone)
Stand-alone PRM platforms available on the market need to be integrated with Dynamics 365 Sales (or other CRMs), which introduces challenges that do not exist when PRM operates directly within the Dynamics 365 ecosystem.
- A separate PRM means maintaining and developing two platforms. Users often need to work in both systems, using similar functionalities on partially synchronised data.
- Due to different platform logic, processes such as tasks, notifications, alerts, and reporting cannot be fully unified. This leads to inconsistent data and slower collaboration across PRM, direct sales, Customer Success, Product, Marketing, and RevOps teams.
- Two systems also mean two sources of truth. Even with extensive integration, this setup cannot match the level of alignment across objects, activities, automation, and workflows that is possible when CRM and PRM operate within a single Dynamics 365 environment.
2. Building PRM capabilities directly in Dynamics 365
The Microsoft Dynamics 365 platform, combined with Power Apps and Power Platform automation, provides a strong foundation for building and managing a partner channel.
A major advantage of using Dynamics 365 for PRM is the ability to manage all sales and business development channels within a single environment. Shared CRM and PRM processes, common data stored in Dataverse, and unified reporting in Power BI enable consistent processes, metrics, and visibility across teams—without relying on externally integrated tools.
The main challenge of this approach is the need to build a PRM solution from the ground up. This can be time-consuming, require architectural expertise, and involve ongoing support from Dynamics 365 specialists.
Depending on PRM requirements, possible implementation models include:
- Configuring standard Dynamics 365 Sales using Contacts, Leads, Accounts, and Opportunities with specific types, parameters, relationships, and connections, as well as custom workflows and access rights. This approach enables Partner-type Accounts, Potential Partner-type Leads, and Partner-related Opportunities.
- Extending Dynamics 365 Sales with custom entities such as Potential Partner and Partner, including all required logic, relationships, dependencies, data structures, user access rights, and process flows.
- Building an integrated Partner Portal that serves as a partner landing zone, enriched with relevant data, processes, communication capabilities, and automations. Within the Microsoft Business Applications ecosystem, this can be implemented using Power Pages, although its limitations should be carefully analysed.
3. Using ISV-based PRM solutions built on Dynamics 365
An alternative to building custom configurations and modifications in Dynamics 365 is implementing ready-made solutions built on Dynamics 365 and Power Apps models.
Main advantages of using ready-made solutions (ISVs for Dynamics 365, such as Power PRM) include:
- They provide a predefined set of configurations and extensions that can be quickly deployed in the client’s Dynamics 365 environment. This significantly shortens implementation time and reduces project risks related to requirements analysis and prototype validation.
- They are open for further customer self-configuration to address specific needs. In PowerPRM, approximately 80% of the functionality is open for additional configuration by the client, while 20% forms the core that ensures solution integrity and product development aligned with the roadmap.
- They provide a predefined set of PRM processes based on best practices and adoption patterns within the Dynamics 365 ecosystem. The PowerPRM product roadmap delivers new capabilities driven by real PRM user needs and incorporates them into the platform standard.
- They come with a proven Partner Portal approach. While Power Pages is flexible and scalable, it may not meet certain business requirements or allow rapid adaptation to evolving needs. Within PowerPRM, the Partner Portal is built using an alternative technology, enabling higher adaptability to specific requirements, better scalability, and improved cost efficiency.
Summary
You can choose one of three PRM models:
- Lightweight PRM implemented through Dynamics 365 configuration and customisations. This approach fits small partner programs with limited cooperation between direct and indirect sales teams and typically without a Partner Portal.
- Stand-alone PRM supporting the full scope of PRM processes, including a Partner Portal. This model makes sense when deep integration with Dynamics 365 data and processes is not required, Dynamics 365 Sales usage is limited, and the external PRM may become the primary source of partner master data.
- PRM add-on for Dynamics 365 (custom-built or ISV-based), suitable for most other scenarios—especially when Dynamics 365 Sales and/or Marketing are used extensively and customer and partner master data are managed within Microsoft Dynamics 365 (CRM or ERP).
The best choice depends on the required depth of CRM integration, the complexity of the partner program, and the operational scale.
