Atman as the first Internet Service Provider in Poland makes Azure Peering Service available nationwide to boost performance when using Microsoft SaaS services.
Based on any Atman Internet Service, our customer can use Microsoft 365, Teams application or Microsoft public cloud services in more stable, predictable and controlled manner via a dedicated interconnect between Atman and Microsoft.
From now on Microsoft SaaS solutions of the Optimize category obtain substantial optimization and enhanced security guaranteed by Atman SLA parameters ( availability of services in 2021 was 99.987%).
Advantages of Atman Internet with Microsoft Peering
Stable connection to Microsoft public cloud services
Short RTT for services such as Microsoft 365 or Microsoft Teams improves performance
One hop to the nearest Microsoft assets with the use of a dedicated interconnect in Warsaw
No need to obtain own ASN and public IP address range. Every IP range from /32 to /24 is available (client’s PI or Atman’s PA)
Path security, mechanism against route hijacking and leaks. The service based in full on the dedicated interconnect connection between Atman and Microsoft
Low operating costs
Flat fee apart from bandwidth and particular SaaS services.
As an additional component of Atman Internet services, the short-path access to Microsoft is delivered within couple of days.
What Atman guarantees
- Physical Partner Peering with Microsoft (Warsaw)
- Local redundancy for both ports
- Generating registration keys
- SLA-guaranteed capacity
- Link monitoring (availability, utilization)
- IP addresses (if the customer owns no IP ranges)
What customer provides
- Setting up your own account in the Azure portal
- Generating a list of public IP addresses from which communication to SaaS will be established
- Application of keys via Azure Portal
- No fees for data packets used, SaaS services are for free
Ways to get access to Microsoft cloud services via Atman
|Peering via IX||Express Route|
|Quality (SLA)||Unpredictable||Stable, redundant access||According to IX policy||100% stable and full throughput|
|Security||DDoS attack possible||Dedicated interconnect,
|According to IX policy||Private Network|
|Physical requirements||None||None||Physical presence at IX||Private Ethernet Line
(at least two of them)
|Configuration requirements||None||None||Own AS number,
at least /24 IP range,
|Atman Service||Business Internet,
|Microsoft Azure Peering Service||Thinx IX