Skip to main content

Azure Subscription - Lesson learned related to credi card

One of my first project on Microsoft Azure is in production from 2011. More than 4 years the system ran without major issues. Every 4-5 months we released a new version of the product.
We have a maintenance and a support team that has a clear list of check lists that needs to be checked every day, week or month. For example, a health check similar with a smoke test is done every day. Every week, the available space of the storage account is checked. At the end of each month we check the expiration date of certificates and so on.

Running a product on an Azure subscription for so long will force you to have a very good process for maintenance and support team. Of course, this process was not perfect from the first day. The checklist was changed and improved in time.

Last week we discovered that an important check was... forgotten....

You know, each Azure subscription is connected to a credit card that is used for billing. And this credit card expires after 2 or 3 years.
What do you think that happens when the credit card expires and you don't update the credit card information?
Your subscription will be disabled. This means that all the services that you are running on that Azure subscription will be suspended. Of course before this, Microsoft will notify you via emails and you will have plenty of time to update the credit card information.
In our case, something happened and we missed the emails notifications that should have alert us about payments issues. In the end we ended up with the Azure subscription suspended and our system was down for some hours.
Luckily, the Azure support team offered us all the support and re-enabled our subscription until we were able to update the credit card information.

Lesson learned: You should add to the checklist of maintenance and support team all external dependencies or resources that can expire, like credit cards or billing status.

Comments

  1. I appreciate your guidance for uploading about Cloud Computing here. I really need to know about it. Great work!

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...