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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP