Leveraging an existing Microsoft license for a SaaS solution that utilizes Azure Communication Services (ACS) to enable video calls within the platform is a complex scenario. The core of the issue lies in the difference between the licensing for Microsoft Teams as a product and the separate licensing required for ACS.
When users log in to your system using the Graph API for Single Sign-On (SSO), they are using their existing Microsoft accounts, which may include licenses for Microsoft Teams. However, ACS is a separate service that typically requires its own licensing, regardless of whether the users have a Teams license.
The concept of "passing through" a license key from the Graph API during SSO to reduce costs and leverage existing Teams licenses is not straightforward. Microsoft's licensing terms and the technical implementation of such a solution would need to be carefully reviewed. It's important to note that license keys are generally not retrievable via the Graph API, as they are part of the contractual and billing relationship between Microsoft and the licensed organization.
Thanks,
Prasad Das
*************************************************************************
If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.