You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Vendors can't sign in to the Vendor Collaboration Portal after re-onboarding
3
-
description: Steps to troubleshoot when vendors can't access the Vendor Collaboration Portal (VCP) after re-onboarding in Dynamics 365 Supply Chain Management.
2
+
title: Vendors Can't Sign In To Vendor Collaboration Portal After Reonboarding
3
+
description: Steps to troubleshoot when vendors can't access the Vendor Collaboration Portal (VCP) after reonboarding in Microsoft Dynamics 365 Supply Chain Management.
ms.custom: sap:Purchase order procurement and sourcing\Issues with vendor management
14
14
---
15
+
# Vendors can't access the Vendor Collaboration Portal (VCP) after reonboarding
15
16
16
-
# Vendor unable to access Vendor Collaboration Portal (VCP) after re-onboarding
17
+
This article provides troubleshooting steps to help resolve issues when vendors are unable to access the Vendor Collaboration Portal (VCP) after being reonboarded in Dynamics 365 Supply Chain Management.
17
18
18
-
## Symptom
19
+
## Symptoms
19
20
20
-
Vendor attempts to access the Vendor Collaboration Portal (VCP) but encounters the error:
21
+
When a vendor attempts to access the Vendor Collaboration Portal (VCP), the following error message occurs:
21
22
22
23
> The user must have access to at least one vendor.
23
24
24
-
Occurs specifically after a vendor has been re-onboarded and access was previously working.
25
+
This error occurs specifically after a vendor has been reonboarded and access was previously working.
25
26
26
-
## Cause
27
+
## Cause 1: The vendor request isn't in "Request approved" status
27
28
28
-
This issue can occur if:
29
-
30
-
- The vendor request may not actually be in **Request approved** status.
31
-
- The **Vendor collaboration access** permission may have been set to **No** during approval.
32
-
- Required **External roles** might not have been assigned to the vendor user.
33
-
- Tenant and user mapping may be out of sync, especially for portals relying on internal data sync mechanisms (e.g., Microsoft Support–only tools).
34
-
- The vendor may still be attempting to log in with incorrect credentials (not using their assigned **work account**).
35
-
36
-
## Resolution
37
-
38
-
Follow these steps to resolve the issue:
39
-
40
-
### Step 1: Verify vendor request status
29
+
**Resolution:**
41
30
42
31
Make sure the vendor request status is set to **Request approved**.
43
32
44
33
For details about checking vendor request status, see [Vendor requests](/dynamics365/supply-chain/procurement/vendor-onboarding#vendor-requests).
45
34
46
-
### Step 2: Check vendor collaboration access
35
+
## Cause 2: The "Vendor collaboration access" permission is set to No during approval
36
+
37
+
**Resolution:**
47
38
48
-
Verify whether the **Vendor collaboration access** permission was set to **Yes** during the vendor request approval.
39
+
If it's set to **Yes**, the vendor user should already have the appropriate roles assigned automatically.
49
40
50
-
- If it was set to **Yes**, the vendor user should already have the appropriate roles assigned automatically.
51
-
- If it was set to **No**, you can manually grant the necessary roles to the vendor user instead of restarting the onboarding process.
41
+
If it's set to **No**, you can manually grant the necessary roles to the vendor user instead of restarting the onboarding process.
52
42
53
43
> [!NOTE]
54
-
> You don’t need to start the onboarding process over if this setting was missed. You can assign the vendor roles manually.
44
+
> You don't need to restart the onboarding process if this setting was missed. You can assign the vendor roles manually.
55
45
56
46
For details about setting up vendor collaboration access, see [Approving a vendor request](/dynamics365/supply-chain/procurement/vendor-onboarding#approving-a-vendor-request).
57
47
58
-
### Step 3: Confirm external roles
48
+
## Cause 3: Required "External roles" aren't assigned to the vendor user
49
+
50
+
**Resolution:**
51
+
52
+
Verify that the vendor user's account includes the roles defined for the _Vendor_ type in **External roles** after reonboarding.
59
53
60
-
Verify that the vendor user’s account includes the roles defined for the _Vendor_ type in **External roles** after re-onboarding.
61
54
For details about setting up vendor collaboration security roles, see [Set up vendor collaboration security roles](/dynamics365/supply-chain/procurement/set-up-maintain-vendor-collaboration#set-up-vendor-collaboration-security-roles).
62
55
63
-
### Step 4: Perform data synchronization
56
+
## Cause 4: Tenant and user mapping out of sync
57
+
58
+
Tenant and user mapping might be out of sync, especially for portals relying on internal data synchronization mechanisms (for example, Microsoft Support–only tools).
59
+
60
+
**Resolution:**
64
61
65
62
If the vendor still can't access the VCP portal, data synchronization might be required.
66
63
67
64
This step can only be completed by **Microsoft Support advocates**. If you're a customer or partner, contact Microsoft Support to perform the following steps in the Microsoft Volume Licensing Support Portal (MVLSP):
68
65
69
66
1. Sign in to the **MVLSP** portal.
70
-
2. Go to **Quick Tasks > View Tenant Mapping**.
67
+
2. Go to **Quick Tasks** > **View Tenant Mapping**.
71
68
3. Select the correct **Purchase Account**.
72
69
4. Select **Update MSDN Managers** to refresh the user mapping data.
73
70
74
-
### Step 5: Ask the vendor to retry login
71
+
## Cause 5: Vendor using incorrect credentials
72
+
73
+
The vendor might still try to sign in using incorrect credentials (not using their assigned **work account**).
74
+
75
+
**Resolution:**
75
76
76
-
After completing the previous steps, ask the vendor to sign in again using a **work account**.
77
+
After completing the previous troubleshooting steps, ask the vendor to sign in again using a **work account**.
77
78
78
-
For details about vendor onboarding and login steps, see [Vendor onboarding](/dynamics365/supply-chain/procurement/vendor-onboarding).
79
+
For details about vendor onboarding and sign-in steps, see [Vendor onboarding](/dynamics365/supply-chain/procurement/vendor-onboarding).
79
80
80
81
> [!TIP]
81
82
> If the issue persists, review the vendor collaboration setup and user role assignments to ensure no conflicting configurations exist.
0 commit comments