Thanks for reaching out. Custom Vision data is stored in azure blob and owned by Custom Vision team, and access is protected through JIT which is a general guideline for azure services. Azure Custom Vision automatically encrypts your data which protects your data and helps you to meet your organizational security and compliance commitments. By default, your subscription uses Microsoft-managed encryption keys, however, you can also manage your subscription with Customer-managed keys (CMK) which offers greater flexibility to create, rotate, disable, and revoke access controls. Customer-managed keys are only available for resources created after 11 May, 2020. Also, customers have full control over viewing, exporting, and deleting their data using the Custom Vision Training APIs. Once you delete the resource/project, the data will be deleted permanently from our blob storage and not recoverable. For more information on compliance and privacy, please refer to Azure Cognitive Services Compliance and Privacy. Hope this helps.
Custom Vision Data Storage
I am working in Azure Custom Vision and I uploaded my images into my project via the Custom Vision Portal. I am curious where this data is stored. Is this data stored within the project? Is it stored in blob storage or file storage or queue storage? Is the data stored away from the project in blob storage or only within the project? If it is only stored within the project, then what type of storage is used?
Furthermore, once a model is trained, where are the model data stored? (e.g. model weights, architecture, etc)
I need this information for security clearance of my azure resource through my enterprise.
Thank you for your time and consideration.
2 answers
Sort by: Most helpful
-
-
Steven De Lausnay 1 Reputation point
2021-11-15T11:01:47.723+00:00 Is it in the mean time already possible to use custom storage account for Custom Vision Service?
We have a customer which is uploading data to a storage account and I just want to bind this to Custom Vision Service to be used for tagging and training, they don't want to upload all the files again in the Portal to do analysis. Even further, the complete setup is private so the storage account is only accessible using private end-points.