{"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.Data Sovereignty in AI: Microsoft Foundry and Regulated IndustriesKey Topics CoveredData Sovereignty FundamentalsWhat data sovereignty means in the context of AI and cloud platformsGeographic and vendor-specific data restrictionsContractual obligations around data processingMicrosoft Foundry ConsiderationsOverview of Microsoft Foundry's LLM deployment capabilitiesUnderstanding the Foundry marketplace for modelsCritical distinction: Azure-hosted vs. third-party hosted modelsHow data flows through different model providersOrganizational Risk FactorsThe gap between infrastructure teams and compliance requirementsWhy systems administrators may not be aware of data sovereignty agreementsPII (Personally Identifiable Information) handling concernsIntellectual property risksBest PracticesVerify data sovereignty requirements before model deploymentReview contractual agreements for data usage restrictionsEnsure communication between technical and compliance teamsUnderstand where your data is being processedMain TakeawaysNot all models in Microsoft Foundry are created equal - Some are Azure-hosted, others are third-party, affecting where your data goesTeam alignment is critical - Infrastructure engineers need visibility into data sovereignty requirementsRegulated industries must exercise extra caution - Healthcare, finance, and other regulated sectors face additional compliance risksCheck before you deploy - Always verify data agreements before spinning up new AI modelsResources MentionedMicrosoft FoundryAzure cloud environmentWho Should ListenData engineers and infrastructure teamsCompliance officers and legal teamsIT decision-makers in regulated industriesAnyone working with sensitive or regulated...","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}