Azure-docs: Can't migrate LUIS Apps to Azure Resources

[jbeltranluna]

While trying to migrate apps to Azure Resources I got the following error message:
"BadArgument: Endpoint keys were assigned by collaborators to your apps and you have no access to them. Either remove these keys or get access. Keys: {keyPath: /subscriptions/f51aa7db-a3d5-4790-xxxx/resourceGroups/ACCChatBot/providers/Microsoft.CognitiveServices/accounts/accchatbotluis, region: WEU, appId: 274bf9f7-a295-xxxx}"

I have checked all my apps and none of them are collaborated. Furthermore, I even deleted all of my apps and I still get the same error.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: fd1b7924-7392-c538-9961-40c92e8a38c1
• Version Independent ID: 9b1991ad-d980-83db-4de8-aa5de13da335
• Content: Migrate to an Azure authoring resource - Azure Cognitive Services
• Content Source: articles/cognitive-services/LUIS/luis-migration-authoring-steps.md
• Service: cognitive-services
• Sub-service: language-understanding
• GitHub Login: @diberry
• Microsoft Alias: diberry

[RohitMungi-MSFT]

@jbeltranluna Thanks for the feedback. We are investigating into the issue and will update you shortly.

[RohitMungi-MSFT]

@jbeltranluna To lookup the error details of your migration could you please submit the details from LUIS portal through "General inquiry through user voice"? This would send the details to our product team who would have access to lookup the logs and provide feedback on the error.

[jbeltranluna]

Yes, I already have opened the issue from the feedback menu. I'll let you know if there is some general solution. Thanks

[RohitMungi-MSFT]

@jbeltranluna Thanks for sharing the feedback through user voice. Our product team should help you further to check your resource migration. We will now proceed to close this thread.

[jbeltranluna]

Hello,

Sorry for reopening the issue. The LUIS product team contacted me through email with a possible solution:

• Use the LUIS API to remove every collaborator from the App

I replied to the email ([email protected]) that I am trying to do that but I always get an unauthorized error (only for the AppId that is giving me the error on the migration, the other AppIds work well with the LUIS API):
{
"error": {
"code": "401",
"message": "The apps - Get application info Operation under LUIS Programmatic APIs v2.0 API is not supported with the current subscription key and pricing tier LUIS.S0."
}
}

I'm reopening the issue just because I'm not sure that the Product Team will get my answer to the solution since I only have as a contact an email address ([email protected]) that I suppose is an automated mail account.

Thank you!

[RohitMungi-MSFT]

@jbeltranluna I am reaching out internally for help. In the meanwhile could you please elaborate the API used for the message seen above? It looks like 2.0 was used, you can try to use 3.0-Preview API's to check if the operation can be successful.

[RohitMungi-MSFT]

@jbeltranluna Could you also confirm if you are using the authoring key while calling the API?

[jbeltranluna]

Hello, it seems my messages are getting to the Product Team, but I don't think they are understanding me. It seems to me that there is an old deleted LUIS App that got stuck somewhere.

Yes, when I use an authoring to key to get the details of the app it says that there isn't any app with that ID in my subscription. When I use a prediction key on that app, the API says that the endpoint is not supported with that key.

I've got an error during the migration saying that an AppID (274bf9f7-a295-4863-8d1b-d2c641e7d261) has keys assigned, but I don't have that AppID anymore, so I cannot unassign those keys. This is what I get when a run " LUIS Programmatic APIs v3.0-preview apps - Get applications list" with my authoring key:

Pragma: no-cache
Apim-Request-Id: eb04e04d-4804-43c2-bd3b-044dfb4e17d8
Request-Id: eb04e04d-4804-43c2-bd3b-044dfb4e17d8
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Request-Context: appId=cid-v1:26a3540d-a02a-4998-a060-715488fd769b
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store, proxy-revalidate, no-cache, max-age=0, private
Date: Thu, 07 Nov 2019 10:44:19 GMT
Content-Length: 2
Content-Type: application/json; charset=utf-8

[]

As you can see, the list of Apps is empty...

[diberry]

@jbeltranluna I believe the service team is now clear on what is going on, thanks to @RohitMungi-MSFT.