When trying to open the LUIS portal (luis.ai) we get the error To continue using the LUIS portal, please migrate your apps to an Azure authoring resource. We could use the portal this morning and everything was working fine. Then suddenly this error occurs and we can't open the portal anymore. It happens to our entire team. Even after refreshing or logging out and logging in again.
The thing is that we are already using an Azure authoring resource. We have always used an Azure authoring resource from the moment we started working with LUIS. So I'm fairly sure that this error is incorrect.
What is going on? What do we do? Does anyone else have this problem?
Related
When using Composer for the first time I created an app in luis and connected from Composer to the Luis app with the key.
In Azure the luis resources were created - (when the resources are created in Azure there is a resource-instance and resource-instance-authoring created, not sure the difference between the two).
I then wrote the bot in Composer.
After finishing the bot in Composer I let Composer publish and provision the Bot in Azure in a new resource group. It did this successfully.
When it publishes to Azure it creates a new luis instance and instance-authoring in the newly created resource group.
When I go to the newly created authoring instance in luis there is nothing there, because that isn't the authoring instance I initially used to write the bot and it says the managed identity is disabled.
And in Azure under in AzureBot/Properties where it says "luis app ids - view values as json" this is empty.
Is there a way to use the data from one luis instance (the instance that was used when the bot was written) and transfer that information to the newly created instance that Composer creates when publishing to Azure?
I ask these questions for the issues i'm having now, but also, in the future if I create a new bot in composer and set it up in luis - and then have Composer publish the new bot - it will create a separate luis authoring instance and i think i'll be in the same position as i am now.
Thanks
Not easily. At least with regards to provisioning. Composer unfortunately wasn't designed that way. Ideally the best way is to provision LUIS first and then utilize that authoring resource to author the LU and then publish when ready. Also; since your app is in the prediction resource, but nothing is in the authoring resource, you can export them from either the previous/working authoring resource or the prediction resource and import into the new authoring resource. Then you can then author and publish from there to prediction. Of course, this authoring would be for minor things like further training of intents.
I hope somebody can help me with this issue.
I recently moved my azure pipeline approval release process from slack web hook to Azure pipeline App for slack, because I found that having the approve and reject button directly in slack chat was something really nice to have to make approvals easier.
This is the process I follow:
Install Azure pipeline App in slack workspace
Create a private channel and /invite #azpipelines
I signed in /azpipelines signing
Once those steps has been completed, I started to subscribe my release pipelines selecting the stages I was interesting in. Everything worked just fine for a couple of days, I was receiving the notifications and I was able to approve and reject them without any problem, which is great, but today, out of nowhere I realised that I was receiving the emails from azpipelines that a release has been issued but no notification in channel.
The documentation about azure pipeline is really poor and I have no idea what is going wrong with the configuration.
Did this happen to anyone before and can direct me on the right path of what could be the issue behind it?
Thank you very much for any help you can provide
Sometimes, I also could encounter the similar problems.
And many times, I can fix the issue via the following ways:
Unsubscribe and re-subscribe the notifications.
Log out and then log in again.
Uninstall and re-install the Azure Pipelines App.
May be you also can try this steps to see if the issue can be resolved.
I'm looking at using the Bot Framework (https://docs.botframework.com) is it possible to register a bot programmatically e.g via service? I see there are Azure bots but still don't see a way to register via service?
At the moment you have to manually log into the portal to register the bot and obtain your keys. There has not been any indication from Microsoft that this will change in future.
from what I know about the goals of the dev team, since this is a highly requested feature, we will probably see this in action in future version of the bot framework.
But no kind of timeline yet for this feature.
Open browser
Navigate to http://www.windowsazure.com/en-us/
Select portal top right
login with my email address
Receive the below error
https://manage.windowsazure.com/Error/Login?getsupport=true&f=255&MSPPError=-2147217320
Receive the error
" We are having trouble logging you into the portal
Please contact Customer Service for assistance."
Using IE or Chrome, incognito or not, cookies cleared or not, cache cleared or not. The problem still exists. Also tried on multiple devices media centre PC, desktop running windows 7, iPhone 5, ipad 3...
Prior to November 2012 I have accessed the windows azure subscription without a problem.
I clicked the customer service link and the australian number is 13 20 58 I have contacted that number explaining that I cannot access my windows azure subscription and each time I login I receive an error. They proceed to redirect me to other support teams where I repeat my details and the problem they either redirect me again or provide a number to call.
In one case I was redirected to a number that no longer exists. Another I was told to raise a case on the windows azure portal page the same portal page that I receive an error on when logging in, when I asked for alternative options there were none.
So far I've spoke with the msdn support team, windows subscription support, online services, etc and still no resolution. In the latest call to support they have said to raise the issue on the forums so here goes.
Anyways long story short I have probably spent 3+ hours calling Microsoft support explaining the problem, waiting on hold, being redirect, repeating... still I can't access my windows azure subscription
I checked in commerce.microsoft.com and there is a windows azure subscription associated with my email address
Subscription-1
Windows Azure MSDN - Visual Studio Premium
Does anyone have any suggestions on how to resolve this issue?
Some time it's happened wait for while and retry
or just ask azure support in twitter
Editing for those who are like me and skipped reading the comments (in small font) below the OP's question. This was resolved and was due to the first reason I list below. However, it could (and has) happen in past for other reasons as well, so might as well keep this response here in case it helps someone else out.
Try logging at https://portal.azure.com/
The manage.windowsazure.com isn't even DNS resolvable to any website - I am not sure how you are getting that address (maybe its from some part of Azure IAM pipeline that hasn't been updated) and (more interestingly) how you are able to open that link - Maybe this is something available only in your region ! (but I am stretching here).
Regardless, I also tried to find other instances of similar issues and in general I see this issue is related to cases when the an account has been transitioned to Office 365.
Here an account was moved and resulted in creation of two accounts with different passwords - solution here was to set the Office 365 account (new account) as a co-admin on the old account that was used to setup the Azure account.
Here the account was not provisioned correctly in Azure AD Store and had to be removed and re-created using DirSync
Here, the problem seems to be related to (the new) Account Provisioning in Azure AD.
In general, it seems this is a problem that might be harder to explain to level 1 support. You might have better mileage speaking to your organizations IT admin and have them check for any inconsistencies that might be similar to those stated above.
Try forcing the directory in the URL like so
https://portal.azure.com/#domain.name
For example in case of MS AAD domain
https://portal.azure.com/#mycompany.onmicrosoft.com
In case of custom domain
https://portal.azure.com/#mycompany.com
Sometimes there is some odd behaviour with redirect loops or when you no longer have access to the tenant but you have selected 'last visited' in the Startup directory.
Glad to hear this was resolved by support. Since this was posted, we made a number of updates to the login process and types of accounts (incl. the addition of MFA). At TechEd we announced a new portal (video # http://channel9.msdn.com/Blogs/Windows-Azure/Azure-Preview-portal) if you want to see what is coming.
In the old silverlight portal, azure cache was under the service bus category along with ACS. In the new HTML5 portal, I can't find my cache anywhere. Under ServiceBus, it says I have zero, and only shows a link to create a new service bus namespace. Should I contact support?
You have to use the previous portal for managing the Azure Cache. Since the new portal is still in beta - not all features have been ported yet. MSDN still links to the previous portal for provisioning the Azure Cache.
Update by question asker: As seen in the comments, it looks like my browser may have been hanging onto a DNS redirect from windows.azure.com to manage.windowsazure.com. I was able to successfully get back to the silverlight portal using both the provisioning the Azure Cache link and by using #BrentDaCodeMonkey's suggestion.