Genesys Cloud CX

 View Only
Discussion Thread View

Microsoft Direct Routing Deprecation for sip-all FQDN's starting March 1rst 2022

  • 1.  Microsoft Direct Routing Deprecation for sip-all FQDN's starting March 1rst 2022

    Posted 01-11-2022 10:53
    In December, 2021 Microsoft released the following notice:

    sip-all FQDNs will not be supported starting March 1st, 2022


    We're making some changes to Teams Direct Routing

    On March 1, 2022, we will be removing support for and FQDNs from Direct Routing configuration.

    Note: If you aren't using Session Border Controllers you can safely disregard this message.

    How this will affect your organization:

    When this change is implemented, if no actions taken and sip-all FQDN is used, users will no longer be able to make or receive calls via Direct Routing.

    What you need to do to prepare:

    Customers will need to use the recommended subnets ( and for any classification or ACL rules and discontinue using the sip-all FQDN when configuring Session Border Controls for the Direct Routing.

    What Genesys Cloud customers need to know

    • Genesys Cloud customers leveraging an SBC for MS Teams telephony integration, need to ensure their SBC configuration will not be impacted.
    • "sip-all" was a mechanism to dynamically manage inbound ACLs with DNS domain names
    • Genesys documentation did not specifically mention how to configure inbound ACLs; rather, it refers to Microsoft documentation.
    • Inbound ACLs should now be managed by static IP ranges, specifically and (the latter added March 2020).
    • For inbound ACLs of the third-party SBCs, customers *should* ensure both ranges are included for seamless support of Direct Routing – the addition of new ranges can be done at any time and will not effect operation, it will only allow Direct Routing to continue to work when Microsoft starts using the new range.


    Jason Wolfgang
    Genesys - Employees