Fix Dynamics 365 Customer Voice Problems

This is the step nobody checks first, and it causes so much wasted time. Dynamics 365 Customer Voice requires either a Dynamics 365 enterprise license or a Microsoft 365 license. That sounds simple, but in practice there's a lot of nuance, especially if your organization has a patchwork of legacy licenses.

To check a user's assigned licenses, open the Microsoft 365 Admin Center at admin.microsoft.com. Go to Users > Active users, click the user having the problem, and select the Licenses and apps tab. You'll see every license assigned to that account. Look for a Dynamics 365 plan or a Microsoft 365 Business/Enterprise plan. If they only have something like a standalone Office license or a Teams Essentials plan, they won't get access to Customer Voice.

For GCC tenants specifically, I want to call this out because the Microsoft documentation is explicit about it, you must have one of those two license types. There's no workaround. If you're a GCC customer and your users are getting access denied errors, the license check isn't optional; it's the first thing to verify with your Microsoft account team.

After confirming the license is assigned, give it up to 24 hours to propagate, though in my experience it usually kicks in within 1–2 hours. You can speed it up by having the user sign out and back in. If the license looks correct and the user still can't access Customer Voice, the next issue is almost always the security role, which we'll cover in Step 3.

If you're seeing this on a freshly created tenant or a new Dataverse environment, also confirm that the Power Apps plan or Dynamics 365 plan includes Dataverse capacity. Customer Voice stores all survey data in Dataverse, and if your environment has zero database capacity allocated, the app will install but immediately fail to function.

The number one panic I hear from users after the transition is: "All my surveys are gone." They're not gone. They've been reorganized, and once you understand the new structure, everything makes sense.

In Dynamics 365 Customer Voice, the top-level container is called a project. A project can hold multiple surveys that share common metrics and settings. When Microsoft migrated your Forms Pro account, each individual Forms Pro survey became its own separate project, one project, one survey each. This means if you had 20 surveys in Forms Pro, you now have 20 projects, each containing exactly one survey.

To find them, sign in at customervoice.microsoft.com and click the All projects tab. Don't look on the Home tab, that only shows recently accessed projects and won't show everything. On "All projects" you'll see the full list of everything migrated over. If you had shared surveys in Forms Pro, those come over as shared projects, and the collaborators should still have access.

If a specific survey still isn't showing up, check that you're in the correct Dataverse environment. The environment selector is usually in the top-right corner of the interface. Your surveys are stored in the environment where Forms Pro was active. If someone switched the default environment after migration, you might be looking at an empty environment while your data sits in a different one.

One important note: all your existing survey responses came along for the ride. Any distribution channel that was active, email, embedded link, QR code, Power Automate flow, continues to accept responses without any action on your part. The surveys didn't stop working during migration. They just moved to a new home.

If a user can log into the Dynamics 365 Customer Voice portal but gets an access denied error or can't create surveys, edit projects, or view reports, the security role is misconfigured. This is especially common after the transition from Forms Pro because Microsoft renamed the security roles during migration.

The old Survey Owner role in Forms Pro is now called Project Owner in Dynamics 365 Customer Voice. If you or your admins built any custom security roles based on the old "Survey Owner" permissions, for example, to create a read-only survey viewer role, those custom roles may need to be updated to reference the new entity names.

Microsoft also added a brand-new role called Customer Voice – Add on. This role is automatically assigned to users who had forms-related permissions in the old system, and it provides User-level permission on the new entities that didn't exist in Forms Pro: Customer Voice project, Customer Voice satisfaction metric, and Customer Voice localized survey email template. If a user can see their old surveys but can't access satisfaction metrics dashboards or create new projects, the most likely fix is assigning them this "Customer Voice – Add on" role.

To assign a security role, open the Power Platform Admin Center, navigate to your environment, click Settings > Users + permissions > Users, find the affected user, and click Manage security roles. Add the Project Owner role for full survey management access, and Customer Voice – Add on for the new entity permissions. Save and have the user refresh their session.

After the role change takes effect, ask the user to navigate back to customervoice.microsoft.com and check that the All projects tab populates correctly and that they can open a project and view the Reports section. That's your confirmation the security role fix worked.

Email templates are a common source of confusion after the Forms Pro to Dynamics 365 Customer Voice migration, because the way they work changed significantly. I know this is frustrating if you had carefully crafted templates for different survey campaigns, here's exactly what happened and what you can do about it.

All email templates you created in Forms Pro were retained and migrated over as personal email templates in Customer Voice. They didn't disappear. However, here's the important change: you can no longer edit those original templates from within the old Forms Pro interface (obviously, since that interface is gone). To use them, you need to import them into your surveys in Customer Voice.

To import a personal email template, open the survey in Customer Voice, go to the Send tab, click Email, then look for the option to select a template. There's an import option that lets you pull in your personal templates. Select the template you want and it gets associated with that survey's send configuration.

If you were previously using different email templates for different language audiences, say, an English template and a Spanish template for the same survey, Customer Voice now has proper support for this as multilingual email templates. You can create a single template that contains locale-specific variations rather than managing separate templates per language. This is actually a real improvement over the Forms Pro approach, even if getting there requires some setup work.

Email templates in Customer Voice are also now stored directly in your Microsoft Dataverse environment. When you copy a project (something you can do via the project's action menu), the email templates configured for that project's surveys automatically copy over to the new project. That's a time-saver if you're spinning up a new feedback campaign based on an existing template. You don't have to manually re-import anything.

If you're on a US Government Community Cloud (GCC) tenant and your survey emails are silently failing to reach respondents, the root cause is almost always Exchange Online sending limits. This is a Dynamics 365 Customer Voice on GCC behavior that catches a lot of government and regulated-industry teams off guard.

In standard commercial tenants, Customer Voice uses Microsoft's shared survey-sending infrastructure. In GCC, that's not available, instead, survey emails go out through your organization's actual Exchange Online mailboxes. This means whoever is listed as the survey sender is subject to Exchange Online's per-user sending limits. Those limits are documented in the Exchange Online service description, and they're not trivial: Exchange enforces a maximum of 10,000 recipients per day per user, with throttling that kicks in well before that ceiling.

If you're distributing a large survey and hitting these limits, the first thing to check is the Exchange message trace in the Exchange Admin Center at admin.exchange.microsoft.com. Go to Mail flow > Message trace, enter the sender's email address, and set the date range to when the survey sends were happening. Look for "Throttled" or "Failed" delivery statuses. That confirms Exchange is the bottleneck.

The fix has a few angles. First, distribute your survey send over multiple days rather than blasting all respondents at once, Customer Voice's scheduling feature lets you stagger sends. Second, if your organization is eligible, work with your Exchange administrator to configure a dedicated service account mailbox for survey sending with appropriate limits. Third, for GCC customers needing FedRamp-certified access, make sure you're accessing the portal at https://customervoice.microsoft.us, not the standard customervoice.microsoft.com. Using the wrong URL causes authentication and routing problems that look like delivery failures but are actually session issues.

Once you confirm the Exchange trace shows successful delivery, go back into Customer Voice and check Reports > Survey invitations to verify that response tracking is working correctly on the platform side.