New in version: 2.13.0
This guide shows you how to secure your FastMCP server using Azure OAuth (Microsoft Entra ID). Since Azure doesn’t support Dynamic Client Registration, this integration uses the OAuth Proxy pattern to bridge Azure’s traditional OAuth with MCP’s authentication requirements. FastMCP validates Azure JWTs against your application’s client_id.
Configuration
Prerequisites
Before you begin, you will need:- An Azure Account with access to create App registrations
- Your FastMCP server’s URL (can be localhost for development, e.g.,
http://localhost:8000) - Your Azure tenant ID (found in Azure Portal under Microsoft Entra ID)
Step 1: Create an Azure App Registration
Create an App registration in Azure Portal to get the credentials needed for authentication:1
Navigate to App registrations
Go to the Azure Portal and navigate to Microsoft Entra ID → App registrations.Click “New registration” to create a new application.
2
Configure Your Application
Fill in the application details:
- Name: Choose a name users will recognize (e.g., “My FastMCP Server”)
- Supported account types: Choose based on your needs:
- Single tenant: Only users in your organization
- Multitenant: Users in any Microsoft Entra directory
- Multitenant + personal accounts: Any Microsoft account
- Redirect URI: Select “Web” and enter your server URL +
/auth/callback(e.g.,http://localhost:8000/auth/callback)
-
Expose an API: Configure your Application ID URI and define scopes
- Go to Expose an API in the App registration sidebar.
- Click Set next to “Application ID URI” and choose one of:
- Keep the default
api://{client_id} - Set a custom value, following the supported formats (see Identifier URI restrictions)
- Keep the default
- Click Add a scope and create a scope your app will require, for example:
- Scope name:
read(orwrite, etc.) - Admin consent display name/description: as appropriate for your org
- Who can consent: as needed (Admins only or Admins and users)
- Scope name:
-
Configure Access Token Version: Ensure your app uses access token v2
- Go to Manifest in the App registration sidebar.
- Find the
requestedAccessTokenVersionproperty and set it to2: - Click Save at the top of the manifest editor.
In FastMCP’s
AzureProvider, set identifier_uri to your Application ID URI (optional; defaults to api://{client_id}) and set required_scopes to the unprefixed scope names (e.g., read, write). During authorization, FastMCP automatically prefixes scopes with your identifier_uri.3
Create Client Secret
After registration, navigate to Certificates & secrets in your app’s settings.
- Click “New client secret”
- Add a description (e.g., “FastMCP Server”)
- Choose an expiration period
- Click “Add”
4
Note Your Credentials
From the Overview page of your app registration, note:
- Application (client) ID: A UUID like
835f09b6-0f0f-40cc-85cb-f32c5829a149 - Directory (tenant) ID: A UUID like
08541b6e-646d-43de-a0eb-834e6713d6d5 - Client Secret: The value you copied in the previous step
Step 2: FastMCP Configuration
Create your FastMCP server using theAzureProvider, which handles Azure’s OAuth flow automatically:
server.py
Important: The
tenant_id parameter is REQUIRED. Azure no longer supports using “common” for new applications due to security requirements. You must use one of:- Your specific tenant ID: Found in Azure Portal (e.g.,
08541b6e-646d-43de-a0eb-834e6713d6d5) - “organizations”: For work and school accounts only
- “consumers”: For personal Microsoft accounts only
Important: The
required_scopes parameter is REQUIRED and must include at least one scope. Azure’s OAuth API requires the scope parameter in all authorization requests - you cannot authenticate without specifying at least one scope. Use the unprefixed scope names from your Azure App registration (e.g., ["read", "write"]). These scopes must be created under Expose an API in your App registration.Testing
Running the Server
Start your FastMCP server with HTTP transport to enable OAuth flows:Testing with a Client
Create a test client that authenticates with your Azure-protected server:test_client.py
- Your browser will open to Microsoft’s authorization page
- Sign in with your Microsoft account (work, school, or personal based on your tenant configuration)
- Grant the requested permissions
- After authorization, you’ll be redirected back
- The client receives the token and can make authenticated requests
The client caches tokens locally, so you won’t need to re-authenticate for subsequent runs unless the token expires or you explicitly clear the cache.
Production Configuration
New in version: 2.13.0
For production deployments with persistent token management across server restarts, configure jwt_signing_key and client_storage:
server.py
Parameters (
jwt_signing_key and client_storage) work together to ensure tokens and client registrations survive server restarts. Wrap your storage in FernetEncryptionWrapper to encrypt sensitive OAuth tokens at rest - without it, tokens are stored in plaintext. Store secrets in environment variables and use a persistent storage backend like Redis for distributed deployments.For complete details on these parameters, see the OAuth Proxy documentation.Environment Variables
New in version: 2.12.1
For production deployments, use environment variables instead of hardcoding credentials.
Provider Selection
Setting this environment variable allows the Azure provider to be used automatically without explicitly instantiating it in code.Set to
fastmcp.server.auth.providers.azure.AzureProvider to use Azure authentication.Azure-Specific Configuration
These environment variables provide default values for the Azure provider, whether it’s instantiated manually or configured viaFASTMCP_SERVER_AUTH.
Your Azure App registration Client ID (e.g.,
835f09b6-0f0f-40cc-85cb-f32c5829a149)Your Azure App registration Client Secret
Your Azure tenant ID (specific ID, “organizations”, or “consumers”)
This is REQUIRED. Find your tenant ID in Azure Portal under Microsoft Entra ID → Overview.
Public URL where OAuth endpoints will be accessible (includes any mount path)
Issuer URL for OAuth metadata (defaults to
BASE_URL). Set to root-level URL when mounting under a path prefix to avoid 404 logs. See HTTP Deployment guide for details.Redirect path configured in your Azure App registration
Comma-, space-, or JSON-separated list of required scopes for your API (at least one scope required). These are validated on tokens and used as defaults if the client does not request specific scopes. Use unprefixed scope names from your Azure App registration (e.g.,
read,write).Azure’s OAuth API requires the
scope parameter - you must provide at least one scope.Comma-, space-, or JSON-separated list of additional scopes to include in the authorization request without prefixing. Use this to request upstream scopes such as Microsoft Graph permissions. These are not used for token validation.
Application ID URI used to prefix scopes during authorization.
Azure authority base URL. Override this to use Azure Government:
login.microsoftonline.com- Azure Public Cloud (default)login.microsoftonline.us- Azure Government
.env file:
server.py

