Customer Voice Login: Access Dynamics 365 Customer Voice

TL;DR

• Commercial-cloud users sign in at customervoice.microsoft.com; GCC users who require the government service use customervoice.microsoft.us.
• If Home and All projects load but the expected project does not, verify the tenant, license, Dataverse environment access, Project Owner role, and project sharing.
• Customer Voice includes 2,000 responses per month at the tenant level for the eligible licensing paths described in Microsoft’s current licensing guidance; capacity does not replace user access.

How do you access Dynamics 365 Customer Voice?

For a commercial Microsoft tenant, open Customer Voice, sign in with the work account in the tenant that owns the surveys, and select All projects. GCC users who require the government service should use its separate address. If the expected project is absent, continue with the tenant, environment, role, and sharing checks below.

Use this direct login sequence:

1. Open the correct Customer Voice URL for your Microsoft cloud.
2. Sign in with the organizational account licensed in the tenant that owns the surveys.
3. If Microsoft asks you to choose an account or directory, select the work account and tenant that contain the relevant Dynamics 365 environment.
4. Open All projects to see projects you created and projects shared with you.
5. Select the required project, then open its survey, report, or distribution area.

The expected landing page matters when diagnosing access. Microsoft’s overview of Dynamics 365 Customer Voice says a successful sign-in presents the Home and All projects tabs. The All projects tab is the central list; it is not necessary to enter Customer Voice through Dynamics 365 Sales or Customer Service first.

Which Customer Voice URL should you use?

Tenant type	Sign-in URL	Important caveat
Commercial Microsoft cloud	customervoice.microsoft.com	Sign in with the account in the tenant where Customer Voice is licensed and configured.
US Government Community Cloud (GCC) requiring FedRAMP-certified services	customervoice.microsoft.us	Microsoft says GCC customers need either a Dynamics 365 enterprise license or a Microsoft 365 license.

Do not use the old Microsoft Forms Pro sign-in route as your Customer Voice bookmark. Customer Voice is the current product, and the current service entry point is the Customer Voice domain.

What access must be in place before login works?

A successful Customer Voice session relies on more than a password. The user needs access at the tenant, environment, and project levels. Confirm an eligible license or service plan, entry to the correct Dataverse environment, the required Customer Voice privileges, and ownership or sharing of the specific project before troubleshooting the browser.

1. The account must be enabled and licensed

The user must be able to sign in through Microsoft Entra ID and must have an eligible product or service plan. Customer Voice is included with select Dynamics 365 enterprise products; inclusion should not be assumed from any Dynamics 365 subscription. Microsoft’s current Customer Voice licensing instructions explain the main paths:

• Select Dynamics 365 enterprise products include Customer Voice access.
• Organizations without an eligible enterprise product can purchase Customer Voice separately.
• A Customer Insights organization must also obtain and assign the free Customer Voice User Subscription License (USL) to each user who needs access.
• The standalone path also requires the free USL for each user who needs access.

Microsoft currently documents 2,000 responses per month at the tenant level with eligible enterprise licensing or a standalone Customer Voice license. That is response capacity, not a substitute for assigning the appropriate user entitlement. For an admin walkthrough, see how to check Microsoft Dynamics 365 licenses by user.

2. The user must be able to enter the Dataverse environment

Customer Voice projects are connected to Power Platform environments, and their survey invitations and responses are stored in the environment selected when the project is created. General Dataverse access requires an enabled account, a recognized license or active per-app plan, membership in the environment’s Microsoft Entra security group when one is assigned, and at least one Dataverse security role. Microsoft lists these checks in its Power Platform user-access troubleshooting guide.

This distinction explains a common symptom: the user can open Customer Voice, but a specific environment is unavailable when creating a project.

3. Project creators need the Project Owner role

To work with Customer Voice projects in a Dynamics 365 environment, the Customer Voice app must be installed there and users must have the Project Owner security role. Microsoft’s environment connection and privileges guide documents both requirements.

A custom security role is possible, but it must include the required permissions for the Customer Voice tables. Treating a generic Dynamics 365 role as equivalent can leave a user able to enter the environment but unable to create or manage Customer Voice projects. Our guide to role-based access in Dynamics 365 explains how Dataverse privileges and access levels fit together.

4. Existing projects must be owned by or shared with the user

All projects does not show every project in the tenant. It shows projects the signed-in user created and projects shared with that user.

When a project owner shares a project, the recipient becomes a co-owner. Microsoft says a co-owner can create, edit, update, delete, and share the project, subject to specific restrictions on surveys created by other users. Use the Share command inside Customer Voice; Microsoft’s project management documentation warns against manually changing the associated Microsoft Entra group or Dataverse team because that can create permission mismatches.

How do admins prepare an environment for Customer Voice?

If users can sign in but cannot select the required environment, an administrator should verify that environment rather than changing tenant-wide settings first. Confirm the Customer Voice app installation, the user’s environment entry, security-group membership, and Project Owner privileges in the exact Dataverse environment where the project will be created or opened.

1. Open the target environment in the Power Platform admin center.
2. Confirm that the Dynamics 365 Customer Voice app is installed.
3. Confirm that the user is enabled and present in the environment.
4. If the environment is restricted by a Microsoft Entra security group, confirm that the user is a member.
5. Assign the Project Owner role, or a tested custom role with the required Customer Voice table privileges.
6. Ask the user to sign out, sign back in, and check All projects or create a project again.

Microsoft notes that Customer Voice entities are already installed in organizations for Dynamics 365 Sales, Customer Service, Marketing, and Talent. Administrators should still verify the actual environment rather than assume that an app installed elsewhere in the tenant covers it.

If you need help aligning the environment, security model, and rollout, review our Dynamics 365 services for implementation and support options.

Why can you log in but not see a Customer Voice project?

The most likely causes are the wrong tenant or missing project sharing. A successful Microsoft sign-in proves identity authentication, but it does not prove that the selected directory owns the environment or that the project owner shared the project with that account. Check those two boundaries before changing licenses or security roles.

Work through these checks:

• Confirm the tenant. A person with accounts in several organizations may authenticate successfully to the wrong directory. Sign out, use a private browser window if needed, and choose the tenant that owns the Dynamics 365 environment.
• Open All projects. Customer Voice places created and shared projects there, including projects across environments.
• Ask the owner to share inside Customer Voice. The owner should open the project menu, select Share, and add the user. Direct Microsoft Entra group edits are not the supported sharing workflow.
• Check whether the project was deleted or recreated. A copied project is a separate project and may need to be shared again.
• Check the account type. Microsoft explicitly states that invited Microsoft Entra B2B users cannot use Dynamics 365 Customer Voice in its Power Platform B2B collaboration guidance.

How do you fix “permission required” or an empty environment list?

Start with the Power Platform diagnostic rather than repeatedly changing browser settings. It checks the affected user’s license, sign-in state, security-group membership, and Dataverse roles in the selected environment. Record its findings before granting broader permissions, because an empty environment list and a project-level access failure have different causes.

An environment administrator can:

1. Open the Power Platform admin center.
2. Select the affected environment.
3. Go to Settings > Users + permissions > Users.
4. Select the affected user.
5. Select Run diagnostics.
6. Review the license, sign-in, security-group, and security-role findings.

The Microsoft troubleshooting procedure also recommends checking whether the user is enabled for sign-in, belongs to the environment’s associated security group, and has a Dataverse security role. If a license or group membership was just changed, allow time for synchronization or refresh the user from the environment’s user management page.

If the environment appears but project creation fails

Check whether the Customer Voice app is installed in that specific environment. Microsoft states that choosing an environment without the app produces an error during project creation. Then confirm the Project Owner role and any privileges needed for custom tables that the survey will use.

If the service opens under the wrong account

Sign out of Microsoft accounts in the browser, open a private window, and return to the correct Customer Voice URL. Enter the intended work email explicitly. This separates an identity-selection problem from a license or Dataverse permission problem.

If an admin disabled the Customer Voice service plan

In the Microsoft 365 admin center, inspect the user’s Licenses and Apps settings. Customer Voice can be disabled as an app under an otherwise eligible Dynamics 365 enterprise license. Microsoft’s licensing page lists the Customer Voice service-plan entries associated with eligible products.

What should you see after gaining access?

The Home tab provides recent projects and satisfaction metrics. The All projects tab lists each available project’s name, modified date, surveys, responses, and environment. From there, a user with the right access can create a project from a template or a blank project and choose its Dataverse environment.

For a first access test, use a low-risk verification:

1. Open All projects.
2. Confirm that the expected environment is available.
3. Open an existing shared project, or create a temporary blank project if your governance policy permits it.
4. Confirm that the survey editor and report area load.
5. Remove the temporary project if it is not needed.

Do not test access by deleting or editing production survey data. Microsoft also warns not to delete Customer Voice data directly in Dataverse because direct deletion is not synchronized with Customer Voice services.

Customer Voice access checklist

Before escalating a sign-in issue, record the result of each item below. The completed checklist separates authentication, licensing, environment authorization, Customer Voice privileges, and project sharing, giving the administrator a reproducible failure boundary. Include the affected tenant, environment, user, project, timestamp, and exact message with the escalation.

• Correct commercial or GCC Customer Voice URL
• Correct work account and Microsoft tenant
• Enabled Microsoft Entra sign-in
• Eligible Dynamics 365 or Customer Voice license
• Customer Voice USL assigned when the licensing path requires it
• Membership in the environment security group, if one is used
• Dataverse security role assigned
• Project Owner role or an adequate custom role
• Customer Voice app installed in the target environment
• Existing project shared through Customer Voice
• Member account rather than an invited B2B guest account

That evidence lets an administrator identify whether the failure is at authentication, licensing, environment authorization, or project sharing instead of treating every case as a generic login problem.