Microsoft Azure outage and reported problems map

Official Links for Microsoft Azure

Visit: Official link coming soon

Visit: Microsoft Azure on Twitter

Visit: Facebook link coming soon

Reports by Users

Last 24 Hours

0 reports

Latest reports

Discuss the current status of Microsoft Azure

Read more about Microsoft Azure

Azure, Microsoft's cloud computing platform, empowers businesses with a scalable and flexible infrastructure. Offering a comprehensive suite of services, Azure enables seamless application development, data storage, and AI integration. With global reach and enterprise-level security, Azure is the catalyst for digital transformation, empowering organizations to innovate, scale, and succeed in the dynamic world of cloud computing.

However, it's crucial to be aware of that, like any online service, Microsoft Azure might experience downtime, outages, or other issues that could impact its status. Are you concerned about Microsoft Azure being down? At Entireweb, we constantly monitor and check the status of Microsoft Azure, ensuring its reliability. Whether you're experiencing Microsoft Azure down or simply want to stay updated on its status, you can check with Entireweb when experiencing problems with Microsoft Azure. Stay informed about Microsoft Azure status and its uptime, and make sure you're always updated of its current status and latest downtime.

FAQ - Azure

What types of security measures are in place for this service?

A variety of security features are used, including encryption and access controls, to protect your data and comply with regulations.

What is the pricing structure for this service?

The pricing for this service is based on usage, so you only pay for what you use. There are also free and discounted options for certain services.

Can I access this service from any device?

Yes, this service is accessible from any device with an internet connection. There are also apps available for mobile devices to make access even more convenient.

Reddit Posts - Azure

Issues Mapping Azure Files Storage After ISP Modem Replacement

A few years ago, we transitioned from an on-premises server to using Azure Files Storage for managing our files. To ensure accessibility, we mapped 10–11 Azure folders to drive letters on client wor...

2024-11-23 02:34:43
Posted by u/Haunting-Exit-6009 in r/AZURE
Score: 1 | Comments: 1
  • VPN plus private endpoints. Don’t run SMB over the internet.

Issues reading AD users with Terragrunt (Service principal in Azure pipelines)

2024-11-22 20:12:24
Posted by u/hi_Revz in r/AZURE
Score: 3 | Comments: 3
  • Your admin needs to consent to User.Read.All in the 2nd image if they haven't done so already

Accessing an Azure storage account with a private endpoint from OnPrem

Hey folks I was wondering if anyone has any insights they can give me. I'm setting up a storage account with a private endpoint which I need users to be able to access remotely, but not publicly; the...

2024-11-22 12:57:33
Posted by u/yoleni in r/AZURE
Score: 7 | Comments: 5
  • Yes you need to be create some form of private DNS resolving in Azure, either using DNS servers or private DNS resolvers. The image in this link will show how and why. [What is Azure DNS Private Resolver? | Microsoft Learn](https://learn.microsoft.com/en-us/azure/dns/dns-private-resolver-overview) Or you can create a static A record in your current on-premise DNS zones pointing to the IP address of your Private Endpoint. Although I'm not very fond of it (private endpoint might change the IP address when redeployed), it will work. As a small addition, I assume port 443 is allowed in all the firewalls which might be there in the communication flow.
  • Placing DNS resolver in **resourcegroup3** is kinda weird but ok. Typically you would deploy such resolver centrally, so in your example most likely **resourcegroup2.** >I can't set up the conditional forwarder as the DNS manager OnPrem can't resolve the IP of the inbound endpoint in Azure. That's most likely routing issue, hard to tell why exactly it cannot reach inbound endpoint. >I'm not sure if I should be using the Azure DNS address (168.63.129.16) somewhere. I read in a guide on another site that the 168.63... address should be in the conditional forwarder, but that seems wrong? Not explicitly. It should be used internally by virtual network where DNS resolver is deployed, but from the description you set up it that way. Azure provided DNS vnet options is exactly that. >Doing an nslookup from an OnPrem machine to the [mystorageexample.blob.core.windows.net](http://mystorageexample.blob.core.windows.net/) address shows a 20.x public IP address for the non-authoritative answer. It does show the privatelink and regular non-privatelink aliases. Doing an nslookup from a VM in Azure (on a different spoke completely, but it is also peered to the ***resourcegroup1*** hub) also shows the same info - a 20.x IP address. Your on-prem should have conditional forwarder for [blob.core.windows.net](http://blob.core.windows.net) zone pointing to inbound endpoint of your DNS resolver. And as you said your on-prem DNS cannot reach inbound endpoint so you couldn't setup such forwarder, current behavior is expected. Firstly, I would focus on fixing the resolving from Azure side. As now even Azure VM resolves to public IP. Your Azure vnets should either use your private dns resolver inbound endpoint as DNS server or you need to setup forwarding rulesets for privatelink zone and link to spoke vnet, I prefer the first option
  • There is a lot going on here. How are you doing DNS in azure? Do you have a VM that is doing your DNS? Or are you solely using Azure private DNS zones for DNS? Also, what is each virtual network's DNS setting?
Inga sidor hittades.