D365 Customer Voice licensing + enabling internal users

Source: Claude.ai chat (original: d365-customer-voice-license-tenant-access__f4eb0dba.md) Added: 2026-10-02

Summary

• Customer Voice licensing is both per-user (survey designers/editors need a license) and tenant-pooled (response capacity is counted across the whole tenant: 2,000/mo included; $100 per additional 1,000/mo).
• Respondents don't need a license — only designers and editors do.
• Check for double-buying: Sales Enterprise, Customer Service Enterprise, Customer Insights, Field Service, Marketing, and Human Resources licenses already include Customer Voice + 2,000 responses/tenant/month. The standalone purchase may be redundant.

Key takeaways

• Customer Insights edge case: an org with Customer Insights must also assign the (free) Customer Voice User Subscription License (USL).
• Three levels of access must line up: tenant (license assigned), environment (user enabled in Settings → Security → Users), project (Project Owner security role + optional per-project co-owner share).
• Projects live in a Dataverse environment — confirm it's the right environment (often the client's D365 env rather than the default), especially if you want responses linked to contacts / cases / flows.

Learnings / how to apply

• Add "license double-check" to the opening call of any Customer Voice engagement — easy money saved if the client already owns Customer Insights or similar.
• Codify the three-tier (tenant / env / project) access checklist for Customer Voice user onboarding.
• Watch the "survey data landed in default environment" trap — hard to recover without a project copy.

---