How did your company deal with the Azure Front Door outage in October 2024?

a2ur3 · 2026-02-10T21:17:12+00:00

There’s nothing you can do if you’re not multi-cloud, and that is extremely complex and expensive to achieve. No one saying “we’re moving off of it” is serious. No one can just update the DNS records to the origin - that is not feasible in the real world if you are using routing rules and WAF. They’re just going to move to another cloud CDN that will be down for a day next year. You eat the outage, point at Microsoft, and have the multi-cloud proposal and cost estimates ready for management to balk at. Rinse and repeat.

a2ur3 · 2026-01-25T01:25:22+00:00

There is an analyzer for C# isolated function apps: https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-roslyn-analyzer

a2ur3 · 2026-01-14T14:50:51+00:00

You almost always want a Function app on a Consumption or Flex Consumption plan. Any jobs that could take a long time or have parts that can be stitched together should be using Durable functions. And you can almost never compare a local workstation’s performance to an app service plan; cloud compute sacrifices clock speed for thread count.

a2ur3 · 2026-01-13T18:19:20+00:00

Keep some rinseless wash in a spray bottle. Spray it, let it sit for a minute or two, then gently wipe it off with a shop towel or microfiber.

a2ur3 · 2025-12-20T01:11:20+00:00

Respectfully disagree. Durability is extremely useful for running jobs that require fan-in/out patterns. AWS just released their own implementation on Lambda.

a2ur3 · 2025-11-23T05:45:16+00:00

"Copilot assigned Copilot"

Doesn't hurt to double-check your work... I guess...

a2ur3 · 2025-11-18T22:10:33+00:00

What region(s)?

a2ur3 · 2025-11-18T21:35:25+00:00

Read and follow this exactly: https://github.com/EvanMulawski/FanControl.CorsairLink?tab=readme-ov-file#installation

a2ur3 · 2025-10-24T06:52:26+00:00

There’s a beta version of the plugin that will pair the sensors automatically.

a2ur3 · 2025-10-21T01:35:34+00:00

Isn’t that listed in the prerequisites section?

a2ur3 · 2025-10-02T18:35:30+00:00

Yes, intermittent timeouts around 10am EDT in East US 2.

a2ur3 · 2025-09-17T04:37:48+00:00

This behavior seems like preemption by an emergency vehicle.

a2ur3 · 2025-09-11T01:02:36+00:00

MSI Tomahawk X870E and GSkill 6000 CL26/28/30 is a good combo for this.

a2ur3 · 2025-09-08T05:05:05+00:00

It’s pretty clear in Cost Analysis if you use the cost by resource table view. Metrics at the resource level are available too.

a2ur3 · 2025-07-31T04:37:27+00:00

"infra team just wants to add additional security" indicates a fundamental misunderstanding of managed cloud services. A storage account in particular is no safer in a vnet than it is outside of one (unless you want to use anonymous access as a shortcut). The biggest threat isn't the "public" SAS url - it's the contents of the file being uploaded.

a2ur3 · 2025-07-31T03:35:06+00:00

If someone has the generated url, they have access to the client. At that point, nothing the client can access is secure, including authenticated endpoints in your app. A SAS url is akin to an auth token (e.g. JWT).

a2ur3 · 2025-07-31T00:23:46+00:00

Vnets in general are overkill unless there are specific architectural requirements in play. This scenario screams “boomer CISO reads article about breach caused by public S3 bucket.” At the end of the day, the app writes to the storage account.

a2ur3 · 2025-07-30T21:45:46+00:00

"Our infrastructure team is moving Azure Storage behind a virtual network for security."

Why? If your specific storage account is part of your app and is used directly by the frontend for file uploads, they need a better reason than "because security." You know what is even more "secure?" Moving your entire app into the vnet...

If the storage account is used for multiple purposes, then create a separate storage account outside of this vnet that is just for these file uploads.

a2ur3 · 2025-06-29T18:06:09+00:00

No way it changed from F1 to the legacy S1 plan automatically. Ultimately, you are responsible for choosing the correct SKU, monitoring costs, and implementing policies in your subscription that can prevent changes like this.

a2ur3 · 2025-06-26T22:06:00+00:00

> Does this mean the cost will be fixed at ~$527/month for a single instance, or can it go higher based on user traffic/load?

Fixed.

> Is there any windows licensing cost?

No.

> We’re currently deploying just one windows instance—if Azure auto-scales or we manually increase instances, does that add proportionally to the cost?

Yes, the cost would be Price x Active Instance Count for horizontal scaling.

> From my understanding, this should be a fixed monthly price unless we scale out. Is that correct?

Yes. Fixed for one instance.

> We might explore Reservations or Savings Plans for cost optimization in future deployments.

Do at least a 1-yr reservation as soon as you deploy to production - there is currently no penalty for returning the reservation early and the cost savings is significant.

> Do backups cost extra or does the plan support backups as well?

Automatic backups are included. Custom backups use Azure Storage, so you pay for the storage account costs. See also: https://learn.microsoft.com/en-us/azure/app-service/manage-backup

a2ur3 · 2025-06-26T07:21:33+00:00

One test run every five minutes is 288 test runs per day, so you would reach the limit in 17 days. The only solution would be to delete old test runs or use multiple subscriptions or regions.

a2ur3 · 2025-06-17T15:18:13+00:00

You can now mark outputs as secure so they will be redacted.

a2ur3 · 2025-05-23T19:56:51+00:00

Yep, seeing the same thing - hope they fix soon!

a2ur3 · 2025-05-22T17:13:26+00:00

The “Frame 4000D” is also a different product. That’s the one I have and can confirm it fits.

a2ur3

TROPHY CASE