| page_type | languages | products | ||||
|---|---|---|---|---|---|---|
sample |
|
|
Deploy to Azure using instructions here.
- Overview
- Prerequisites
- Getting Started
- Endpoints
- Troubleshooting
- Need Help
- Contributing
- Resources
- Trademark
- License
In order to properly implement a secure Azure Communication Services solutions, developers must start by putting in place the correct infrastructure to properly generate user and access token credentials for Azure Communication Services. Azure Communication Services is identity-agnostic, to learn more check out our conceptual documentation.
This repository provides a sample of a server implementation of an authentication service for Azure Communication Services. It uses best practices to build a trusted backend service that issues Azure Communication Services credentials and maps them to Azure Active Directory identities.
This sample can help you in the following scenarios:
- As a developer, you need to enable an authentication flow for joining native Azure Communication Services and/or Teams Interop calling/chat which is done by mapping an Azure Communication Services identity to an Azure Active Directory identity and using this same Azure Communication Services identity for the user to fetch an Azure Communication Services token in every session.
- As a developer, you need to enable an authentication flow for the Azure Communication Services support for Teams identities which is done by using an M365 Azure Active Directory identity of a Teams' user to fetch an Azure Communication Services token to be able to join Teams calling/chat.
If you are looking to get started with Azure Communication Services, but are still in learning / prototyping phases, check out our quickstarts for getting started with azure communication services users and access tokens.
📢 An Azure Communication Services Solutions - Authentication Sample (C# version) can be found here.
Additional documentation for this sample can be found on Microsoft Docs.
Since this sample only focuses on the server APIs, the client application is not part of it. If you want to add the client application to login user using Azure Active Directory, then please follow the MSAL samples here.
Before contributing to this sample, please read our contribution guidelines.
To be able to run this sample, you will need to:
- Register a Client and Server (Web API) applications in Azure Active Directory as part of On Behalf Of workflow. Follow instructions on how to set up App Registrations
- Create an Azure Communication Services resource through Azure Portal. Follow Quickstart: Create and manage Communication Services resources to create an Azure Communication Services resource using Azure Portal.
If you're wondering where to get started, here are a few scenarios to help you get going:
- "How does the Azure Communication Services Authentication server sample work?"
- Take a look at our conceptual documentation on:
- "I want to see what this Azure Communication Services Authentication Server sample can do by running it!"
- Check out our local deployment guide guide.
- "I want to submit a fix or a feature for this project"
- Check out our contribution guidelines first.
- Check out the following guides in sequence after coding.
This Azure Communication Services Solutions - Authentication server sample provides responses for user and token endpoints. For more details, please check our Endpoints and Responses designe doc.
-
Maximum number of extensions values supported per application is 2.
An application can add at most two open extensions for an Azure Active Directory user.
Resolution: If more than 2 extensions are required, then Graph Open Extensions cannot be used to persist the Azure Communication Services Identity mapping as in the sample. You need to consider Alternative Identity Mapping as suggested in Architecture Overview. Otherwise, you can delete the extensions following Graph Open Extensions Delete API. You can delete the extension for any user, if you are M365 Tenant/Azure Active Directory Admin. You can use Graph Explorer to execute for a single user.
-
Provided identity doesn't belong to the resource.
This issue happens if there is mismatch of Azure Communication Services Identity persisted within Graph Open Extensions user instance and the Azure Communication Services resource.
The scenario would happen when the Azure Communication Service Identity mapping for a Azure Active Directory user account was created with one Azure Communication Services resource in the deployed sample and the Azure Communication Services resource changed with subsequent deployments.
Resolution: Swap the Azure Communication Services resource used in the deployed sample as was used in prior deployment. Otherwise delete the extension within Graph Open extensions using the resolution step for above issue.
-
For troubleshooting Azure Active Directory Token issues, please refer to Troubleshoot AAD Token.
-
For troubleshooting consent issues during Azure Active Directory authentication flow, please refer to Unexpected user consent error, Unexpected user consent prompt.
-
When running sample application in local, to troubleshoot unexpected error response on APIs, you could use
stacktracepresent in the response. -
When running the sample application in production e.g. Azure App Service, you can enable Application Insights to troubleshoot the Api failures in absence of application logs.
(i) You can refer to Enable Application Insights on App Service for enabling Application Insights on web application deployed on App Service.
(ii) You can refer to Analyze Failures on how to troubleshoot unexpected Api response.
If you are are unable to find solution to the issue you are facing while running the sample on local or on production, you can use Discussions Channel to seek advise.
Join us by making a contribution. To get you started check out our contribution guidelines.
We look forward to building an amazing open source Azure Communication Services Authentication server sample with you!
- Azure Communication Services Documentation - Find more about how to add voice, video, chat, and telephony on our official documentation.
- Azure Communication Services Hero Samples - Find more Azure Communication Services samples and examples on our samples overview page.
- On-Behalf-Of workflow - Find more about the OBO workflow.
- Creating a protected API - Detailed example of creating a protected API.
- Graph Open Extensions - Find out more about Microsoft Graph open extensions.
Trademarks This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.