Get started with the trusted authentication service hero sample

Important

This sample is available on GitHub for node.JS and C#.

Overview

Azure Communication Services requires developers to generate user and access token credentials inside of a trusted authentication service. 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 Microsoft Entra identities.

This sample can help you in the following scenarios:

• As a developer, you need to enable an authentication flow to generate Azure Communication Services user identities mapped to a Microsoft Entra identity. Using this identity you then will provision access tokens to be used in calling and chat experiences.
• As a developer, you need to enable an authentication flow for Azure Communication Services support Teams identities, which is done by using an Microsoft 365 Microsoft Entra identity of a Teams' user to fetch an Azure Communication Services token to be able to join Teams calling/chat.

Note

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.

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 Microsoft Entra ID, then follow the MSAL samples here.

Prerequisites

To be able to run this sample, you will need to:

• Register a Client and Server (Web API) applications in Microsoft Entra ID as part of On Behalf Of workflow. Follow instructions on registrations set up guideline
• A deployed Azure Communication Services resource. Create an Azure Communication Services resource.
• Update the Server (Web API) application with information from the app registrations.

Getting started

If you're wondering where to get started, here are a few scenarios to help you get going:

• "I want to see what this Azure Communication Services Authentication Server sample can do by running it!"

  • Check out our local deployment guide guide.

• "How does the Azure Communication Services Authentication server sample work?"

  • Take a look at our conceptual design documentation. This documentation outlines the internal design of the service.
    • Architecture Overview
    • Secured Web API Architecture Design.
    • Identity Mapping Architecture Design.
    • Token Exchange Architecture Design

Endpoints

This Azure Communication Services Solutions - Authentication server sample provides responses for user and token endpoints. For more details, please check our Endpoints and Responses design doc.

Next steps

Download the sample from GitHub

Additional reading

• 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.

Getting started

If you're wondering where to get started, here are a few scenarios to help you get going:

• "I want to see what this Azure Communication Services Authentication Server sample can do by running it!"

  • Check out our local deployment guide guide.

• "How does the Azure Communication Services Authentication server sample work?"

  • Take a look at our conceptual design documentation. This documentation outlines the internal design of the service.
    • Azure Communication Services Authentication Server Sample Architecture Design.
    • Secured Web API Architecture Design.
    • Identity Mapping Architecture Design.
    • Token Exchange Architecture Design

Endpoints

This Azure Communication Services Solutions - Authentication server sample provides responses for user and token endpoints. For more details, please check our Endpoints and Responses design doc.

Next steps

Download the sample from GitHub

Additional reading

• 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.