At this time, we cannot identify the service causing this. All traffic is expected to remain in India. Kindly help identify which Azure service generated AU East outbound traffic and why.

Question

At this point, we have been unable to identify any specific service or configuration on our side that would intentionally generate outbound traffic from the Australia East region. All primary workloads and services are designed to operate exclusively within India regions, and we expect that data egress should remain localized accordingly.

We would appreciate your assistance in reviewing the billing and traffic details to help identify which Azure service generated the outbound traffic from AU East, the underlying reason for this routing, and any contributing factors involved.

Answer 1

Hi @Aman Sahni,

Thank you for reaching out. I understand the concern regarding unexpected outbound traffic from the Australia East region, especially since your workloads are designed to remain within India.

To help narrow this down, please try the following steps:

1. Review Cost Analysis for the Subscription Navigate to Cost Management → Cost Analysis for the impacted subscription and filter by Location = Australia East. This will help surface any resources—such as VMs, load balancers, storage accounts, or platform services—that may have generated traffic from that region, even unintentionally.

Reference:

2. Check for Resources or Dependencies in AU East In some cases, services may have been deployed or auto‑provisioned in a different region due to defaults, paired-region behavior, failover mechanisms, or configuration dependencies. Please review the list of resources within the subscription to confirm whether any components exist or were previously created in Australia East.

3. Optionally Apply Conditional Access Location Restrictions If you want to prevent access to Azure resources from outside India, you can create a Conditional Access (CA) policy to block authentication attempts based on geographic location. Guidance: https://learn.microsoft.com/en-us/entra/identity/conditional-access/policy-block-by-location

While this does not directly control Azure resource deployment, it can help ensure that only India-based identities access the environment, limiting indirect triggers that might cause non‑India traffic.

Kindly let us know if the above helps or you need further assistance on this issue.

If you need further help please share the details requested over Private message.

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