Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Email-based authoring keys will be retired in LUIS on June 8, 2020 #26

Open
tomkerkhove opened this issue Oct 30, 2019 · 0 comments
Open

Email-based authoring keys will be retired in LUIS on June 8, 2020 #26

tomkerkhove opened this issue Oct 30, 2019 · 0 comments

Comments

@tomkerkhove
Copy link
Member

@tomkerkhove tomkerkhove commented Oct 30, 2019

Email-based authoring keys will be retired in Language Understanding Intelligent Service (LUIS) and is switching to Azure authoring resources.

Deadline: June 8, 2020
Impacted Services: Azure Cognitive Services / Language Understanding Intelligent Service (LUIS)
More information:

Notice

Notice was sent out via email:

Migrate to new Azure resources for Language Understanding authoring authentication

You're receiving this email because you use Language Understanding (also called LUIS), a part of the Azure Cognitive Services family.

To provide more advanced security and authentication features for your Language Understanding apps, we're upgrading the authoring authentication from an email account to an Azure resource.

On June 8, 2020, your current authoring keys will be retired, and you'll need to start using Azure authoring resources. To avoid losing access to your Language Understanding apps, migrate to new resources by that date.

The new Azure resources provide:
• Role-based access control (RBAC), allowing different users to have different > permissions.
• Azure Active Directory (Azure AD) authentication.
• Custom domains.

There's no charge for the Azure authoring resources, and authoring transactions will remain limited to 1 million per month and five per second.

Impact

Access to LUIS apps will be lost in case of no migration

Required Action

Migrate towards the Azure authoring resource approach as described in this guide.

Contact

You can contact them via Azure Support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.