Restricting Modification of Purview Labels
We have a use case where we have a set of files that are going to have a label applied (let's say for dicussion purposes the label that is being applied is "Highly Confidential") using the Azure Purview Scanner (although any method of applying the label should suffice for this use case). That label is not going to be made visually selectable/available to any Active Directory/Azure AD account (meaning it will not be visible to those account in MS Word, MS Excel, MS Powerpoint, Sharepoint or any other application where labeling has been made available and impacts the file itself). All Active Directory/Azure AD user accounts will have access to apply 3 additional labels of "Public", "Internal", and "Confidential" to files that do not meet the qualifiers to be labeled "Highly Confidential". We want a way of preventing any one of those user accounts from modifying or removing the label only when the label applied to the file is "Highly Confidential". We also need to be able to share a subset (this subset is not a fixed number of files) of the files that have the "Highly Confidential" label applied with external parties via Exchange Online. We have attempted to use the permissions made available in the Purview product today to help achieve our use case --- but that also means we have to apply encryption (there is no "OR" option). We have tried numerous methods of applying encryption and at the same time attempting to ensure that the external email experience is seamless (or at least consistent across platforms). Unfortunately, we have been unsuccessul to date (just not a great user experience). So, either we need a way of decoupling permissions and encryption (assuming that will even achieve our end goal) or an alternate solution which allows the user to apply one of the 3 labels I mentioned without the ability to remove/modify the "Highly Confidential" label where it is applied.AI-900: Microsoft Azure AI Fundamentals Study Guide
This comprehensive study guide provides a thorough overview of the topics covered in the Microsoft Azure AI Fundamentals (AI-900) exam, including Artificial Intelligence workloads, fundamental principles of machine learning, computer vision and natural language processing workloads. Learn about the exam's intended audience, how to earn the certification, and the skills measured as of April 2022. Discover the important considerations for responsible AI, the capabilities of Azure Machine Learning Studio and more. Get ready to demonstrate your knowledge of AI and ML concepts and related Microsoft Azure services with this helpful study guide.
Azure Form Recognizer Studio: Custom Classification Models - Training Failing
I've been experimenting with the Form Recognizer Studio's Custom Classification Models. It was working fine last week and then after the weekend break, I cannot get a single model to train correctly. The issues appears to be on Microsoft's backend as I had a teammate try on a different subscription of Azure and they received the same error. Below is me initially uploading my 5 documents and adding a label to them: After I tag 5 documents and hit the train button the model will act like it's training with everything updating my Azure Blob, creating a .ocr.json file for each trained document. The model itself inside of Form Recognizer, models will say it's failed with the error: "InternalServerError: An unexpected error occurred." Screenshot of the Models: Screenshot of the failure: Screenshot of the blob storage: I'm unsure what is causing this error as I was able to use the same documents and everything last week. I even deleted my resource group that was hosting this and recreated everything from scratch.
