Dynamics 365 Supplier Engagement Preview: Global Vendors, Power Pages Portal and March 2027 GA

Tracked under Microsoft 365 Roadmap ID 576758 and detailed in Microsoft Learn's prerelease documentation, Supplier Engagement remains in development following its public preview rollout in July 2026, with general availability currently projected for March 2027. Because Microsoft's roadmap dates are planning estimates and the accompanying Microsoft Learn documentation is explicitly marked as preview guidance subject to change, enterprise IT architects and procurement leads should treat this as a substantial preview-stage capability rather than a finalized commercial release. Even in preview, however, the technical architecture reveals a major shift in how Dynamics 365 handles vendor data, cross-entity governance, and external portal security.

A Three-Part Architecture Across Power Platform and ERP​

Rather than bolting another form onto the legacy ERP interface, Microsoft split Supplier Engagement across three connected environments:

1. The Internal Supplier Engagement App: A model-driven Microsoft Power Apps application built on Microsoft Dataverse. Designed for internal buyers and procurement professionals, it serves as a unified workspace to manage prospective and active suppliers across all legal entities, schedule appointments and supplier reviews, track performance, and oversee registration pipelines.
2. The External Supplier Portal: A supplier-facing web portal built on Microsoft Power Pages. It gives prospective vendors a public entry point to register and gives approved suppliers a self-service workspace for onboarding, requests for quotation (RFQs), managed bidding, purchase order confirmations, consignment inventory tracking, and invoice submissions.
3. Dynamics 365 Supply Chain Management and Finance: The core ERP environment continues to anchor operational procurement processes, shared supplier master data, financial workflows, and feature configuration, automatically synchronizing changes with Dataverse and the Power Apps workspace.

According to Microsoft Learn's data architecture documentation, Supplier Engagement is intended to replace the older Vendor Collaboration module in Supply Chain Management, though Microsoft's roadmap notes that the new portal also works alongside existing vendor collaboration capabilities. For IT administrators, the practical takeaway is clear: you are no longer inviting external suppliers directly into a pared-down module of the Supply Chain Management interface. Instead, external interactions are decoupled onto Power Pages while data synchronizes back to the ERP core.

Section Summary​

• Status: Currently in public preview (since July 2026), with general availability targeted for March 2027 on the Worldwide (Standard Multi-Tenant) cloud.
• Core Stack: Combines a model-driven Power Apps workspace on Dataverse, an external Power Pages supplier portal, and Dynamics 365 Supply Chain Management and Finance.
• Strategic Shift: Decouples external vendor self-service from direct ERP access while unifying multi-entity supplier management.

The "Global Vendor" Model: Ending Multi-Entity Duplication​

Why does managing a single multinational supplier often feel like managing ten different companies? In traditional ERP setups, if a parent organization operates across five different regional subsidiaries (legal entities), procurement staff frequently have to maintain five separate vendor profiles, duplicating contact lists, addresses, and ISO compliance certificates every time something changes.

Microsoft Learn's preview documentation shows that Supplier Engagement addresses this directly by introducing the global vendor concept. A global vendor record acts as a single master profile in Dataverse and Supply Chain Management that represents a supplier across all legal entities, linked to a single party record in the global address book. Individual relationships with specific subsidiaries are still represented as local vendor accounts, which buyers can release from the global profile to specific legal entities to manage local bank accounts, approved product categories, and country-specific tax or regulatory fields.

Crucially, only vendors associated with a global vendor record can be accessed through the Supplier Engagement app or the external supplier portal. Organizations migrating to this model do not have to start from scratch; Supply Chain Management includes tools to convert existing local vendor records into global vendors or merge existing accounts under a single global profile.

Within the Dynamics 365 Supply Chain Management interface, administrators and buyers can view these records by navigating to Procurement and sourcing > Vendors > Supplier engagement > All global vendors. This form tracks the global vendor's name, ID, status, active holds, and released local vendors.

Section Summary​

• Master Record: The global vendor profile acts as a single source of truth tied to one Global Address Book party across all legal entities.
• Cascade Benefits: Compliance certificates entered at the global vendor level automatically apply to all linked local vendors, cutting down repetitive administrative data entry.
• Reporting Upgrades: Turning on Supplier Engagement upgrades the built-in Supply Risk Assessment report (Procurement and Sourcing > Inquiries and Reports > Supply Risk Assessment > Supply Risk Assessment) with date filtering and global vendor aggregation.

Inside the Supplier Portal: Staged Onboarding and Access Boundaries​

From a cybersecurity and governance standpoint, opening an enterprise procurement portal to the public internet requires strict staging. You want prospective suppliers to be able to raise their hands and apply without giving unvetted users access to sensitive bidding or invoicing workspaces.

Microsoft Learn's portal documentation outlines a multi-stage gatekeeping workflow that separates anonymous registration from authenticated onboarding and active transactions:

Stage 1: Anonymous Initial Registration​

The Power Pages landing page is publicly accessible without authentication and can be branded with the buying organization's logo, color scheme, and layout. A prospective supplier selects Register, reviews the instructions, and completes a Global Vendor registration request form covering basic company info, contacts, capabilities, and certifications, followed by confirmation checkboxes and a security CAPTCHA. Submitting the form sends an acknowledgment email to the prospect and queues the request inside the internal Supplier Engagement Power App for buyer review.

Stage 2: Authenticated Onboarding Wizard​

Approval of an initial registration does not immediately make the company an active, transactable vendor. Instead, the approved prospect receives an invitation to the portal, and a user is provisioned with the Global Vendor Admin role. When that user signs in via Login > Entra user, the portal intercepts them with a mandatory onboarding wizard:

• Contact Information: Requires primary communication details and at least one physical address before proceeding.
• Company Details: Captures business profile metrics (founding year, employee count) and ownership diversity classifications.
• Capabilities: Uses a buyer-configured tree control to map out product categories, market segments, capabilities, and quality standards.
• Certificates: Allows the vendor to log compliance certificates, effective/expiration dates, and upload supporting documentation.
• Assessment Questionnaire: Prompts the supplier to answer buyer-configured yes/no and free-text vetting questions.

Even during this authenticated stage, prospective vendors only see a simplified portal home page. Transactional workspace tiles remain hidden until the onboarding wizard is finalized and internal procurement staff formally qualify and approve the global vendor record.

Stage 3: Transactional Collaboration and User Governance​

Once qualified and approved, the portal unlocks operational workspaces for responding to RFQs (including tracking won and lost bids), confirming or responding to purchase orders, monitoring consignment inventory levels and consumption, and creating or tracking invoices. Microsoft notes one important backend dependency here: before suppliers can submit invoices through the portal, the buying organization must configure the vendor invoice workflow in Supply Chain Management.

What happens when a large supplier needs ten different account managers and billing clerks to use the portal? Vendor administrators can go to Setup > Users to deactivate former employees immediately or submit requests to add new users and assign local vendor access. Crucially, external vendor admins cannot unilaterally provision new users into your environment—every new access request must be reviewed and approved by the buyer's internal staff inside the Supplier Engagement app, which then synchronizes the approved access rights with Supply Chain Management.

Section Summary​

• Strict Gatekeeping: Registration, onboarding, and qualification are separated into distinct stages; transactional tiles remain hidden until a vendor is formally qualified.
• Buyer-Controlled Provisioning: While supplier admins can manage roles and immediately deactivate their own users, adding new portal users requires explicit buyer approval inside the Supplier Engagement app.

Hard Technical Prerequisites and Preview Limitations​

If your IT and ERP teams are considering spinning up Supplier Engagement in a sandbox environment ahead of its projected March 2027 general availability, pay close attention to the deployment requirements documented on Microsoft Learn. Connecting a model-driven Power App, a Power Pages portal, and a Finance and Operations environment involves rigid version dependencies and a few notable preview caveats:

• Supply Chain Management Version: Your environment must be running Dynamics 365 Supply Chain Management version 10.0.48, build 10.0.2645.52, or later.
• Virtual Entity App and Solutions: The Power Platform environment must be connected to Supply Chain Management via Dataverse and run the Finance and Operations Virtual Entity app at version 2.20.3385.8 or later. Administrators must also verify in the Power Apps maker portal (Solutions > Managed tab) that four specific managed solutions are installed: Dynamics 365 Company, Dynamics Operations Virtual Entity Support, Microsoft Operations ERP Catalog, and Dynamics 365 ERP Virtual Entities.
• Dedicated Service Account (No App Registrations): For installation, cloud flows, notifications, and background automation, Microsoft requires a dedicated standard Microsoft Entra ID user account with all required licenses—explicitly noting that an Entra app registration account cannot be used. This service account must hold the System Administrator role in Dataverse, the System Administrator role in Supply Chain Management, and the Power Platform administrator role in Microsoft Entra ID.
• US English (LCID 1033) Language Constraint: During the current public preview, the Supplier Engagement app is only available in US English (LCID 1033). Because a Dataverse environment's base language is locked in during provisioning and cannot be changed afterward, installing the preview on a non-English base environment can result in a jarring mixed-language UI where Dataverse system labels appear in the local language while Supplier Engagement labels appear in English. Microsoft recommends testing the preview on a Dataverse environment provisioned with US English and states that additional languages will be added for general availability.
• Unsettled Commercial Licensing: While the feature is provided for preview evaluation and the Power Pages supplier portal offers a 30-day trial period, Microsoft states that the final licensing model for Supplier Engagement features in Supply Chain Management and the Dataverse app is still under review and will be published prior to general availability.

What Enterprise IT and Procurement Teams Should Do Now​

Supplier Engagement is a well-architected answer to a long-standing Dynamics 365 pain point. By elevating vendor master records to a cross-entity global profile in Dataverse and moving external collaboration onto Power Pages, Microsoft gives procurement teams a cohesive workspace without compromising ERP security boundaries.

At the same time, veteran administrators know better than to bet a production rollout on unfinished licensing terms or a single-language preview. If your organization struggles with multi-entity vendor duplication or relies heavily on the legacy Vendor Collaboration module, the smartest move right now is to provision a US English (LCID 1033) sandbox environment running Supply Chain Management 10.0.48 (build 10.0.2645.52+) and test how existing local vendors convert and merge into global vendor records. Keep production cutover plans penciled in for spring 2027, and wait for Microsoft to finalize multi-language support and commercial licensing entitlements before retiring your existing vendor workflows.