When trying to create a new Local Network Gateway I'm getting an error for the submission saying 'This offer is not available for subscriptions from Microsoft Azure Cloud Solution Providers'.
My account is 'owner' of the subscription (so it has Microsoft.Network/LocalNetworkGateways create / write permissions) and the subscription itself has Microsoft.Network resource provider already registered (I created successfully vNet and a vNet Gateway).
No idea if missing something from subscription or some setting for CSP we work with? Subscription uses 'pay as you go' plan.
Any hints? TIA
I also contacted MS Q&A and they provided some workarounds (1st one worked for me), acknowledging the issue.
Thank you for reaching out. I just went through similar issues using our internal tooling and found that below work-arounds worked for the customer. Can you try the steps mentioned below and see if that fixes the issue.
Do a "Hard Refresh" (F5) on the page and see if that fixes the issue. (This helped resolve the issue for most of the customers.)
Create using the following URL: https://link.edgepilot.com/s/b7b99a1c/OHp2IQfsYESVtpZFaOHItA?u=https://portal.azure.com/?feature.canmodifystamps=true%26Microsoft_Azure_HybridNetworking=flight1%23home
Create using PowerShell: Connect your on-premises network to an Azure VNet: Site-to-Site VPN: PowerShellAzure VPN Gateway | Microsoft Docs
Looks like this is a known issue and the team is currently working on fixing it.
Related
I configured on-premise date gateway by downloading and installing from the Microsoft Azure-analysis documentation which I published below. However, I also found an option to create the same from Microsoft Azure-analysis portal.
Here I am trying to understand the difference before I attempt to create from Azure-portal. Would any please help me understand. Thank you for giving your valuable time.
Thank you David Browne - Microsoft posting your suggestion as answer to help other community members
Gateway created from (as per your screen shot): On-premises Data gateway that you can create from portal (as per your screen shot), Allows access to your on-premises data for Logic Apps service through the data gateway.
reference : https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-gateway-connection
Gateway created from Azure analysis page: The on-premises data gateway provides secure data transfer between on-premises data sources and your Azure Analysis Services servers in the cloud. Those are separate steps for configuring a gateway for use with Azure Analysis Services
Reference: https://learn.microsoft.com/en-us/azure/analysis-services/analysis-services-gateway
Unable to Create web app bot from Azure portal.
Getting error like this "We're having problems communicating with the server. Click to contact Azure Support."
I have tried near 5 different location but the result is same.
Can anyone help me in this.
The issue was mitigated. Could you please re-try and let us know?
Kindly review the Service health page on the Azure Portal to find more details on this issue.
The ‘Service Health’ -Service issues view shows any ongoing problems in Azure services that are impacting your resources. You can understand when the issue began, and what services and regions are impacted. You can also read the most recent update to understand what Azure is doing to resolve the issue.
I've tried un-registering and re-registering and it just keeps getting stuck. No logs I can see so I'm not really sure what to do...
Has anyone experienced this before?
It appears that there was some issue, which is now mitigated. Check your Service Health/Resource Health page.
The ‘Service Health’ - Service issues view shows any ongoing problems in Azure services that are impacting your resources. You can understand when the issue began, and what services and regions are impacted. You can also read the most recent update to understand what Azure is doing to resolve the issue.
Resource health helps you diagnose and get support when an Azure issue impacts your resources. It informs you about the current and past health of your resources and helps you mitigate issues. Resource health provides technical support when you need help with Azure service issues.
Reference:
https://learn.microsoft.com/en-us/azure/service-health/resource-health-overview
If its a brand new subscription i always like to deploy a new Resource manager VM to register all the required resource provider. Once the VM deploys OKs then you can try the AKS (Kubernetes) deployment.
Note: you might still need to register Microsoft.ContainerService for AKS
While you wait for support you can try that an see. Don't forget to delete the VM.
This appears to be an issue that pops up on occasion. As far as I can tell there's no self-service way to fix this when it happens, and your only recourse is to file a support request via the Azure Portal here: https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview
I wanted to create a "Redis Cloud" via the Azure marketplace but I didn't found this service in the marketplace list.
Doesn't it exist anymore? Why?
Or is there some kind of limitation, e.g. it's only available for certain types of Azure subscriptions?
I'm wondering because via redislabs.com I can still choose "Azure" for creating a Redis Cloud - but not via Azure marketplace.
Sadly, you are right Munchkin.
I've looked into the matter and it appears that our Redis Cloud plugin is stuck in limbo between the old and new portals. This is an Azure team issue and we're waiting for a resolution from them.
Until this is rectified, note that you can always create a direct subscription via our website however and do feel free to contact our support team with any questions.
You can find it in the "New Portal" Azure Marketplace, http://portal.azure.com. There you should be able to find it listed as "Redis Cache" or Redis Cloud, first one is Managed by Microsoft, the second one is IaaS on a VM.
I created a Biztalk service (xyz.biztalk.windows.net) as a part of testing hybrid connection for my azure website.
I deleted the biztalk service (xyz) and tried to create a new service with the same name (xyz.biztalk.windows.net).
Azure would not allow me to use the same name (xyz). It gives me this error "the specified name is already in use or is not allowed"
Is there any specific time I need to wait until I can use the service name I deleted?
Any help or information related to this would greatly be appreciated.
According to my experiences with the Azure BizTalk Services Free and Developer tiers, I can only confirm this situation. This is not documented on MSDN as far as I was able to find out.
If this is a URL you where planning to use for a production environment, I suggest you contact Microsoft support.