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.
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
I am trying to load the page 'https://www.customvision.ai' for training Vision Api for improving the object detection ability of Azure Cognitive Service Instance. But it does not getting me to https://www.customvision.ai/projects, fails instead. No error messages in browser console.
I have created a resource for Cognitive Service in West-US2 region in Azure Portal. Do I need to create any more resources specific to Custom-vision? Please suggest.
I am using MSDN Azure Subscription for accessing Azure Portal.
Actually no need to create specific one. Try logging out and switching the subscription. you should be able to access it without a problem if you're under valid subscription
Ashokan, the easiest way to get an answer for your question is
(1) visit https://cognitive.uservoice.com/forums/598141-custom-vision-service
(2) Click "Contact Us"
(3) Report the issue there and submit
This way we'll be able to assist you one-on-one and give you a solution faster.
It was fixed automatically after sometime without me intervening while I am still using MSDN Azure Subscription.
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.
When configuring continuous deployment in Team Project with http://portal.azure.com, I receive the following error:
Unable to locate blade 'ExistingWebsitesPickerBlade' in extension
definition. Search
path:'[0]WebsitesExtension-[1]ExistingWebsitesPickerBlade'.
Any ideas?
There is nothing wrong in the process of what you are doing, but this is indeed a bug where the new portal.azure.com fails to provide you the right blade containing your existing websites to configure continous deployment.
As you can see, this is a fairly regular error that others are experiencing throughout the whole portal experience.
http://devslice.net/2015/04/azure-app-service-orchestrating-business-processes/
There might also be an issue connected to which subscription level you are currently using (ex. BizSpark, Dreamspark, Pay-as-you.go etc.) which makes the portal fail in specific areas because of the former.
Provide adequate details for your subscription level to the Azure support team (create an incident), and they are your best bet at getting through with Continuous Deployment in the new Azure portal.
After yesterday's announcement of BizTalk Service GA on Windows Azure, I'm trying to create a new Development instance so I can start migrating my on premises BizTalk projects to there.
After I fill the wizard and start waiting for the instance creation, I get the following error:
Could not connect to the Tracking Database. Confirm that the SQL Database details are correct and that Windows Azure Services is enabled on the SQL Database. (RDFE - Operation ID = fcc014e60cea345c9e03dcd2dca787d3 )
What is happening?
Make sure DB allows Azure services to access it
Possibly the internal DNS problems are affecting it.
The Register Microsoft pulls its crowd-control tech from out of the shadows
a variety of Microsoft services including Windows Azure and Xbox became unavailable due to an as-yet-unspecified problem with Microsoft's global DNS configuration
or
Xbox One site BELLY-UP in GLOBAL Microsoft cloud catastrophe
Initial reports seem to indicate the problem stems from an internal DNS issue, as both the page and various Azure services are throwing DNS errors. Azure may be working, but reaching it is difficult.