Azure portal displaying bug?

Question

Hello everyone,

I encountered a situation with my Azure account that I could use some help with. Initially, I used an Azure account with a 200€ balance and activated my subscription. With the 200€ starting budget, I created an Azure Managed API Service and set up an HTTP API within it. After upgrading my account, the Managed API Service transitioned from a paused state to resumed. While the API requests are still working as expected, I'm facing an issue where the API itself is no longer displayed in the Azure portal, even though it is actively in use and functioning correctly.

The total number is 0:

The custom Domain settings were not discarded.

There were over 20 HTTP requests that eventually led to an Azure Logic App.

As this is still functional, there is not trigger displayed in the logic app itself.

How is that possible ?

How can i possibly troubleshoot ?

If you have the slightest idea, please let me know!

I would greatly appreciate any insights or guidance on how to resolve this issue. Thank you!

Answer 1

Hi Ben,

Can you check this troubleshooting guide for the API Service - https://learn.microsoft.com/en-us/azure/api-management/diagnose-solve-problems

Also you can raise a support case via the portal so the Microsoft engineer can assist you in this issue - https://azure.microsoft.com/en-ca/support/create-ticket/

Hope this helps.

JS

==

Please Accept the answer if the information helped you. This will help us and others in the community as well.

Answer 2

@Ben Reisinger Thanks for reaching out. I had a discussion with our Engineering team and confirmed that it's a bug and below is the Root cause of the issue.

The Azure Subscription that hosts the Azure APIM was suspended (the Managed API Service transitioned from a paused state to resumed) which caused the Azure APIM instances to get deleted. Due to a bug, the service performed a hard delete, instead of a soft delete for a few days, which caused the control plane to clean up the configuration data within the day.

By the time the Azure subscription was reactivated, service restored, and support ticket opened the database backups had expired and control-plane information was no longer able to be restored.

While this should not happen, we do recommend the customer to adopt infrastructure-as-code as part of their workflows to ensure that the configuration can be easily re-created. This can be achieved by using tools such as Bicep/Azure Resource Manager or APIOps.

We apologize for this inconvenience and will improve our platform to avoid this from happening by implementing a fix and improving our DB backup strategy to ensure we keep copies around for a longer period.

let me know if you have any queries, I would be happy to assist you.

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topic