description:
customers integrating ringcx with microsoft teams, particularly in environments utilizing microsoft entra (azure ad) conditional access policies, require more granular and specific network configuration options. currently, available documentation only provides general ip supernets for ringcx services, which are too broad for organizations that enforce strict security controls such as ip-based allowlisting.

business need:
many enterprise customers implementing conditional access policies prefer or require the use of specific, static ip addresses or smaller ip ranges to restrict access. the lack of dedicated ip ranges for ringcx integrations with microsoft teams (including teams chat functionality) creates challenges in meeting internal security and compliance requirements.

requested enhancement:

provide dedicated or static ip ranges specifically for ringcx and microsoft teams integration traffic
offer more granular ip segmentation (e.g., per service such as teams chat, voice, or api traffic)
publish detailed and integration-specific network documentation for ringcx and microsoft teams
clarify whether certain integration components can support fixed egress ip addresses

expected benefit:
this enhancement would allow customers to implement stricter security controls, simplify conditional access configuration, and improve overall adoption of ringcx with microsoft teams in enterprise environments.

use case:
customer attempting to integrate ringcx with microsoft teams needs to configure microsoft entra conditional access and requires specific ip addresses for allowlisting. current documentation is too general and does not meet security policy requirements, leading to deployment delays and uncertainty.

impact:
improves customer experience for enterprise and security-conscious organizations, reduces support inquiries related to ip allowlisting, and enhances compatibility with microsoft security frameworks.