Forum Discussion
Teams Phone - "You're not setup to use this feature"
You're doing all the right steps, it looks like you're very close!
Yes, policy changes like Shared Calling, Caller ID, and custom Calling policies can take up to 24–72 hours to fully propagate across Microsoft Teams and associated devices, especially on SIP phones like the Poly CCX400.
Here are a few quick suggestions while waiting:
- Confirm policy assignment: Use PowerShell to check if the CallingLineIdentity, VoiceRoutingPolicy, and TeamsCallingPolicy are correctly applied to the Front Desk account (Get-CsOnlineUser -Identity email address removed for privacy reasons).
- Restart the Poly CCX400: After policy updates, reboot the device to force Teams to fetch the latest settings.
- Check outbound PSTN usage record: Ensure the calling policy or voice routing isn’t missing a PSTN usage record needed for outbound calls.
- Test from Teams desktop: Try making the outbound call from the Teams desktop app signed in as the same Front Desk user. If that works, the issue might be device-specific.
- Shared Calling rollout: If Activity Log shows "Rolling out to users," it’s best to give it more time Microsoft’s rollout isn’t instant, especially with resource accounts and shared numbers.
Thanks for taking the time to respond. I may have discovered the issue, although I have yet to test. It appears that in order to use Shared Calling with a single primary number assigned to one Resource Account, you need to choose a "Pay-As-You-Go" license for that account. I was using a Calling Plan license, which may have been the reason the outbound calls were failing. I'm now working with MS to buy some communication credits, but that has revealed a new issue with our account. Hopefully once I'm able to get some credits, I will be able to test this theory of using a PAYG license.