{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The AI Briefing","title":"Data Sovereignty in AI: What You Need to Know About Microsoft Foundry and Regulated Data","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/d441ec0a\"></iframe>","width":"100%","height":180,"duration":187,"description":"Tom discusses critical data sovereignty considerations when using AI platforms like Microsoft Foundry, especially for regulated industries. Learn about the risks of deploying LLMs with sensitive data and how to ensure compliance with geographic and contractual data agreements.\nData Sovereignty in AI: Microsoft Foundry and Regulated Industries\nKey Topics Covered\nData Sovereignty Fundamentals\nWhat data sovereignty means in the context of AI and cloud platforms\nGeographic and vendor-specific data restrictions\nContractual obligations around data processing\nMicrosoft Foundry Considerations\nOverview of Microsoft Foundry's LLM deployment capabilities\nUnderstanding the Foundry marketplace for models\nCritical distinction: Azure-hosted vs. third-party hosted models\nHow data flows through different model providers\nOrganizational Risk Factors\nThe gap between infrastructure teams and compliance requirements\nWhy systems administrators may not be aware of data sovereignty agreements\nPII (Personally Identifiable Information) handling concerns\nIntellectual property risks\nBest Practices\nVerify data sovereignty requirements before model deployment\nReview contractual agreements for data usage restrictions\nEnsure communication between technical and compliance teams\nUnderstand where your data is being processed\nMain Takeaways\nNot all models in Microsoft Foundry are created equal - Some are Azure-hosted, others are third-party, affecting where your data goes\nTeam alignment is critical - Infrastructure engineers need visibility into data sovereignty requirements\nRegulated industries must exercise extra caution - Healthcare, finance, and other regulated sectors face additional compliance risks\nCheck before you deploy - Always verify data agreements before spinning up new AI models\nResources Mentioned\nMicrosoft Foundry\nAzure cloud environment\nWho Should Listen\nData engineers and infrastructure teams\nCompliance officers and legal teams\nIT decision-makers in regulated industries\nAnyone...","thumbnail_url":"https://img.transistorcdn.com/l4TTMAx4d27sGdvCOPP-6vIhh7U0b5J5SpAWtYmxkvs/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8yN2U2/ZWY1ODg4MTgwMjk3/MjVmZmZjODNmMjVh/YzFjNS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}