Deal Registration Consent & Troubleshooting Guide
Deal Registration feature in WeTransact securely connects to Microsoft Partner Center to create, update, and manage your registered deals. To enable this integration, users must grant Microsoft consent so WeTransact can act on their behalf using their authorized Partner Center role. This ensures that only verified referral admins can submit deal registrations, maintain compliance, and keep all activity securely linked to the correct user identity.
The consent prompt ensures compliance with Microsoft’s App + User authentication model. It guarantees that Deal Registration activities performed through WeTransact are authorized, secure, and traceable to a valid Referral Admin user. Without granting consent, Deal Registration cannot function due to Microsoft Partner Center restrictions.
🔐 Why Giving Consent Is Required for Deal Registration (Compliance & Security)
To manage Deal Registrations through the Microsoft Partner Center APIs, WeTransact uses a secure authentication method called App + User authentication. This is a Microsoft-mandated model designed to ensure security, compliance, and proper authorization when a partner interacts with Deal Registration functionality.
When accessing Deal Registration for the first time, users are prompted to:
- Sign in with their Microsoft (Entra ID) credentials, and
- Grant consent to WeTransact.
What this consent allows
By granting consent, the user authorizes the WeTransact platform to impersonate their Partner Center Referral Admin role, strictly for the purpose of:
- Creating deal registrations
- Updating deal registrations
- Retrieving existing deal registrations
This ensures that only authorized individuals from your organization can perform these actions, meeting Microsoft’s compliance requirements.
📘 Why Companies Need This for Compliance
1. Microsoft requires it for security
Deal Registration involves sensitive commercial data — customer names, opportunity value, sales information. Microsoft enforces App + User authentication to ensure that:
- Only users with the Referral Admin role can manage deals
- Actions taken in Partner Center are traceable to a valid user
- Unauthorized automation or system-to-system impersonation is not possible
2. Ensures accountability and auditability
Consent links the API activity to a real person, which supports:
- Internal compliance
- Auditing standards
- Tracking who created or modified deal registrations
Many organizations require this as part of their governance, especially in enterprise environments.
3. Protects your company’s Partner Center environment
Without user consent, WeTransact cannot act on your behalf — ensuring no unauthorized system can manipulate deal data.
4. Required for secure integration with Microsoft systems
This consent is not optional; it is built into Microsoft’s Partner Center architecture. Completing it ensures your organization remains compliant with:
- Microsoft Commerce API rules
- Partner security requirements
- Least-privilege access principles
🛠 Known Issue: Missing Service Principal
Sometimes the consent page breaks or shows an error. This happens when the Microsoft Partner Center service principal is not present in your Entra ID tenant.
To fix it, the service principal must be added manually using PowerShell:
This creates the required Microsoft Partner Center identity inside your tenant so consent can be processed correctly. This can be executed in:
- Any local PowerShell environment
- Azure Cloud Shell (recommended)
🟣 Error: "Please contact Support"
This error usually appears if your access permissions or credentials are incomplete. Follow the steps below to resolve it. 👇🏻
👉🏻 Read more>
🟣 Looping to Same Page
If you're trying to set up the Deal Registration tab on the WeTransact portal and it keeps going in circles and taking you back to the same page.
🟣 Error: "System Error"
If you are attempting to set up the Deal Registration tab on the WeTransact portal and encounter the "system error".