Share via

Narrow Microsoft Teams (Bot Service) IP Ranges

Đino Prenc 0 Reputation points
2026-04-09T09:53:22.5533333+00:00

Hello,

We are currently using Azure Bot Service to create a bot that is integrated with Microsoft Teams (as a Teams app).

While reviewing our logs for outbound Teams messages, we observed that requests are originating from IP ranges associated with AzureCloud North Europe and AzureCloud West Europe.

Our goal is to implement strict IP whitelisting, and therefore we need the smallest possible set of IP ranges. The ranges listed in the official documentation below are too broad for our security requirements: https://dori-uw-1.kuma-moon.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#microsoft-teams

Could you please:

  1. Provide the most granular (narrowest) possible IP ranges specifically required for Azure Bot Service when used with Microsoft Teams?
  2. Confirm which IP ranges are required when the Bot Service is deployed in the West Europe region.
  3. Explain why message traffic appears to originate from general AzureCloud IP ranges rather than from a distinct Azure Bot Service, even though we are using Azure Bot Service for bot configuration.

This information is critical for aligning with our internal security policies.

Thank you in advance for your support.

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vergil-V 11,230 Reputation points Microsoft External Staff Moderator
    2026-04-09T13:25:00.0633333+00:00

    Hi @Đino Prenc   

    Based on my research, I am happy to share the insights I have gathered so far regarding your request. 

    1/ Regarding the most granular IP ranges required for Azure Bot Service when used with Microsoft Teams. 

    The most granular, Microsoft‑supported IP scope for Azure Bot Service traffic with Microsoft Teams is the AzureBotService service tag (including regional variants), which is far narrower than Microsoft 365 Teams or full AzureCloud IP ranges.

    2/ Concerning the IP ranges required when the Bot Service is deployed in the West Europe region. 

    The official and authoritative source for Azure service IP ranges is the Download Azure IP Ranges and Service Tags – Public Cloud from Official Microsoft Download Center file, which can be downloaded from the Microsoft Download Center. 

    After reviewing the JSON file from this download, I identified the entries specific to AzureBotService in the West Europe region. The current address prefixes listed for this service tag are: 

    • 13.69.67.56/30 
    • 40.74.24.64/30 
    • 2603:1020:206:1::20/123 

    undefined

     

    3/ Regarding why message traffic appears to originate from general AzureCloud IP ranges rather than a clearly distinct Azure Bot Service range. 

    The Bot Framework Connector service, which is responsible for delivering messages between Microsoft Teams and your bot endpoint, runs on shared Azure infrastructure. As a result, outbound traffic to your bot can appear to come from Azure public IPs that are also associated with broader AzureCloud service tags. 

    Internally, Microsoft groups the IPs used by Azure Bot Service under the AzureBotService service tag, including its regional variants. These IPs are subsets of broader AzureCloud.WestEurope and AzureCloud.NorthEurope ranges, which explains why traffic may sometimes look more general at the network level. 

    I hope this helps clarify your situation. Please feel free to reach out if you have any updates. 

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.