Unable to provision API Management Instance - Still activating

Question

Unable to provision API Management Instance - Still activating

Nicolas Worth 25

Hi All,

I am relatively new to Azure services and have been tasked with provisioning APIM instance. I have been trying to provision a APIM on the Developer pricing tier. Each time I have tried to provision this the instance is just staying at status "Activating". It has been like this for a few hours now and does not seem to progress any further. I have reviewed the activity log and I am seeing a lot of errors for operation name 'Get token' when inspecting the error is shows the following -

Resource: /subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroup>/providers/Microsoft.ApiManagement/service/<APIMServiceName>/users/1
Operation Name: Get token
Time stamp: Wed Oct 04 2023 12:18:35 GMT+0100 (British Summer Time)
Event initiated by: <MyUserPrinciple>
Error code: InvalidOperation
Message: API Management service is activating

Is this related to why the instance will not activate? or is this error message just misleading and will go away once the instance is provisioned?

I have tried provisioning the APIM using connectivity types "None" and "Virtual network" and still face the same issue.

Any help or advice will be greatly appreciated.

Thanks

Accepted answer

0 additional answers

Your answer

Answer 1

JananiRamesh-MSFT 29,236

@Nicolas Worth Thanks for reaching out. Apologies for the inconvenience caused. Does the issue still persist? This was an ongoing issue, customers using Developer or Basic SKU services may experience long durations or failures/timeouts when creating API Management services or when performing any service update such as adding custom domain, working with managed identity or adding service to a VNET.

Engineering team is working on deploying a short-term fix in the next few days that should address the problem. will revert you back once I have an update.

let me know incase of further 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 topics.

Nicolas Worth 25 Reputation points

2023-10-06T12:43:56.5633333+00:00

Thanks for the update, can you please confirm if the engineering team have deployed the fix. Thanks
JananiRamesh-MSFT 29,236 Reputation points

2023-10-10T17:20:39.45+00:00

Nicolas Worth Thanks for getting back, Issue has been fixed. did you retry? do you still face this issue?
Nicolas Worth 25 Reputation points

2023-10-11T11:23:15.2166667+00:00

Hi @JananiRamesh-MSFT, I appear to still be having issues. With the APIM Instance that I created, I am now trying to update the networking to reside inside my Internal VNET and it is failing to update the API Management Service Instance. I have followed the documentation for the Security group rules and believe they have been setup correctly. In the Activity Log all I am seeing is -

Resource: /subscriptions/<SubcriptionID>/resourcegroups/<ResourceGroup>/providers/Microsoft.ApiManagement/service/<APIMInstanceName>

OperationName: Create or Update API Management Service instance

ErrorCode: ResourceOperationFailure

Message: The resource operation completed with terminal provisioning state 'Failed'.

Kind Regards

Nic
JananiRamesh-MSFT 29,236 Reputation points

2023-10-11T12:07:25.8366667+00:00

Nicolas Worth Thanks for getting back, this needs to be investigated Please send an email to azcommunity@microsoft.com referencing this thread with your subscription ID, APIM resource id /subscriptions/<SubcriptionID>/resourcegroups/<ResourceGroup>/providers/Microsoft.ApiManagement/service/<APIMInstanceName> Please mention "ATTN Janani" in the subject field. I will gladly assist you further.
Nicolas Worth 25 Reputation points

2023-10-11T13:41:15.72+00:00

Ok sent an email, many thanks.
JananiRamesh-MSFT 29,236 Reputation points

2023-10-13T02:23:57.04+00:00

Nicolas Worth Thanks for your patience! From the logs i see that you were trying to deploy APIM in a VNet and it fails with below exception: DependencyResolutionException: An exception was thrown while executing a resolve operation.

This happens if VNET has custom DNS configured. To resolve this issue, you should configure Azure DNS as your custom DNS server's forwarder. please refer: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances?tabs=redhat#name-resolution-that-uses-your-own-dns-server
I also see VNET has NSG and route table configured. I don't see any issue with NGS but the route table has a default route that routes all the traffic to NVA.

please enable service endpoints on the subnet to the below missing services

refer: https://learn.microsoft.com/en-us/azure/api-management/api-management-using-with-vnet?tabs=stv2#force-tunnel-traffic-to-on-premises-firewall-using-expressroute-or-network-virtual-appliance

If you still observe the errors, I suggest you open a support ticket to our Azure Support team. They will help you in configuring the Vnet. Do you have a support plan for this subscription? If not, I can have a one-time free support ticket created to have this specific issue investigated. I will share the details in a separate message after you confirm.

I hope this helps and let me know if any questions.
Nicolas Worth 25 Reputation points

2023-10-13T15:05:37.49+00:00

Good Afternoon Janani,

Many thanks for your guidance on this, the main issue appeared to caused due to the service endpoints being disabled. I enabled those which allowed the APIM to be attached to my VNET. I then had to add a few missing routes to get all the communications to various endpoints working.

It all seems good now, thanks again for your help.

Thanks

Nic
JananiRamesh-MSFT 29,236 Reputation points

2023-10-13T15:42:46.0166667+00:00

Nicolas Worth Glad to hear that the issue is resolved.

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

2024-02-17T06:07:46.22+00:00

Hi , i am getting this issue still with subnet with developer sku. i have enabled the NSG but still its complaining about as below API Management service uses Azure SQL Server internally to store configuration for your service.\nThe service deployment failed to connect to an Azure SQL Server on port 1433 from inside the Virtual Network. \n 1. Please ensure an Azure SQL Server DNS can be resolved, if using a Custom DNS Server.\n2. Please ensure that there is no NSG / Firewall blocking outbound port access on 1433 from the Virtual Network subnet where deployment is being attempted.\nPlease review other common network configuration and troubleshooting information at https://aka.ms/apim-vnet-common-issues"

Share via

Unable to provision API Management Instance - Still activating

0 additional answers

Your answer