MicrosoftDocs
SLA for VNET
[Enter feedback here] We dont see any SLA for VNET. I checked: https://azure.microsoft.com/en-in/support/legal/sla/ and SLA summary page, however do not see any SLA information. I see that we are charging for VNET Peering which also means that this should be backed by SLA. Please let me know where I can find the SLA information for this service
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 07cec477-f584-400f-889c-9a5403f34bad
- Version Independent ID: f777fdfd-2f5a-56b9-574f-ae6d2b19f130
- Content: Azure Virtual Network FAQ
- Content Source: articles/virtual-network/virtual-networks-faq.md
- Service: virtual-network
- GitHub Login: @mbender-ms
- Microsoft Alias: mbender
@Siby22071989, Thanks for your feedback. We shall review this and get back to you soon!
@Siby22071989, Similar to VNet, VNet peering is software-defined and is always available.
We do not charge for peering creation, but for data transfer.
https://azure.microsoft.com/en-us/pricing/details/virtual-network/
Please let me know if you have any further questions on this.
@KapilAnanth-MSFT : Thank you. The Vnet itself is free of charge. However there are charges for peering under Data Transfer ( Inbound/ Outbound ). When Network infra is impacted, the Inbound , Outbound data charges are still present. What is the SLA for these components that are charged.
Hi @Siby22071989,
In case the infrastructure is unavailable, technically there will be no data flow/transfer between the VNets. In case of an outage, Customers will not be charged as no data will be exchanged between the peers.
Hope this clarifies. Please let me know if you have any follow-up queries.
@KapilAnanth-MSFT: Thank you for the details. In this situation the impact happened and there were charges. That is there was intermittent impact and during this time there were egress charges. Question is would these egress/ ingress charges be covered by SLA
Hi @Siby22071989, If that is the case, I would request you to raise a support incident with Azure Billing Team. They can look into this and provide more insights.
