エピソード

  • Entra Workload Identities - Simply Explained

    Entra Workload Identities - Simply Explained
    2026/08/05
    Modern cloud environments are no longer accessed only by people. Applications, automation workflows, Azure services, DevOps pipelines, AI agents, and background jobs all require secure access to business resources without relying on human interaction. In this Microsoft Knowledge Nuggets episode, Mirko Peters explains Microsoft Entra Workload Identities in plain English, showing how software securely authenticates to Microsoft 365, Azure, Microsoft Graph, and enterprise services without storing usernames and passwords inside code. Whether you're an Azure administrator, cloud architect, developer, DevOps engineer, or Microsoft consultant, this episode provides a practical foundation for understanding secure application authentication.UNDERSTANDING USER IDENTITIES VS WORKLOAD IDENTITIESMicrosoft Entra ID manages both human users and software identities, but they operate very differently. Human identities authenticate using passwords, passkeys, Windows Hello, and multi-factor authentication, while applications require non-interactive authentication methods that operate continuously without user involvement. Workload identities provide applications with their own unique digital identity, allowing Microsoft Entra ID to authenticate software independently from human accounts. This separation improves security, eliminates shared service accounts, increases auditing capabilities, and allows every application, automation, or AI workload to receive only the permissions required for its specific business purpose.APP REGISTRATIONS, SERVICE PRINCIPALS, AND MANAGED IDENTITIES EXPLAINEDThree Microsoft Entra concepts frequently confuse administrators: Application Registrations, Service Principals, and Managed Identities. This episode clearly explains the relationship between these components. Application Registrations define the global identity of an application and describe the permissions it may request. Service Principals represent the application's local identity within an individual Microsoft Entra tenant, where administrators grant permissions and enforce security controls. Managed Identities extend this model by allowing Azure resources such as Azure Functions, Logic Apps, Virtual Machines, and App Services to authenticate automatically without developers managing secrets, passwords, or certificates. Together, these identity models create the secure authentication foundation for modern cloud-native applications.HOW MANAGED IDENTITIES ELIMINATE PASSWORDSOne of the most significant security improvements in Microsoft Azure is the ability to authenticate workloads without embedding credentials inside applications. Instead of storing passwords, client secrets, or connection strings within source code, Azure resources using Managed Identities request short-lived access tokens directly from Microsoft Entra ID. The episode explains how authentication and authorization work together, how Azure Key Vault integrates with Managed Identities, and why temporary access tokens dramatically reduce the risks associated with credential theft, secret leakage, source code exposure, and long-lived authentication credentials.SECURING WORKLOAD IDENTITIES IN MICROSOFT AZUREWorkload identities require governance just like privileged user accounts. The discussion explores the importance of least privilege access, Conditional Access for workload identities, workload identity federation, certificate-based authentication, Microsoft Entra ID Protection, logging, monitoring, lifecycle management, and ownership. Mirko explains why every workload identity should have a clearly assigned owner, minimal permissions, continuous monitoring, and regular security reviews. Organizations that neglect application identities often leave behind unused service principals, forgotten secrets, excessive permissions, and automation that continues operating long after the original project has ended.CHOOSING THE RIGHT IDENTITY STRATEGY FOR EVERY WORKLOADSelecting the correct authentication model depends largely on where the application executes. Azure-hosted services should generally use System-Assigned or User-Assigned Managed Identities whenever possible. Applications running outside Azure, including GitHub Actions and external cloud platforms, benefit from Workload Identity Federation instead of long-lived client secrets. Custom enterprise applications often require Application Registrations and Service Principals, while certificates provide a more secure alternative to client secrets when Managed Identities are unavailable. By combining Microsoft Entra Workload Identities, Azure Key Vault, Microsoft Graph, Zero Trust principles, and least privilege access, organizations can significantly strengthen application security while simplifying authentication across Microsoft 365 and Azure environments.Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
    続きを読む 一部表示
    17 分
  • Azure Platform Engineering, Azure Landing Zones, Cloud Adoption Framework & Building Enterprise Cloud Platforms Jev Suchoi [MVP]

    Azure Platform Engineering, Azure Landing Zones, Cloud Adoption Framework & Building Enterprise Cloud Platforms Jev Suchoi [MVP]
    2026/08/05
    Moving workloads into Microsoft Azure is only the beginning of a successful cloud journey. Building a cloud platform that is secure, scalable, automated, and developer-friendly requires a completely different mindset. In this episode of M365.FM, Microsoft MVP Jev Suchoi explains how Platform Engineering helps organizations build reusable cloud foundations that enable innovation while maintaining governance, security, and operational excellence. The discussion explores Azure Landing Zones, Infrastructure as Code, Cloud Adoption Framework, DevOps, automation, and modern enterprise cloud architecture through practical real-world experience.

    UNDERSTANDING AZURE LANDING ZONES AND CLOUD FOUNDATIONS
    Azure Landing Zones provide the standardized architecture that allows organizations to deploy workloads consistently across Microsoft Azure. Jev explains how Landing Zones establish networking, identity, security, governance, subscriptions, policies, and management services before application teams begin deploying workloads. Rather than treating Azure like a traditional datacenter, organizations should build cloud-native platforms designed for scalability, automation, and self-service. The conversation also explains why Microsoft's Enterprise Landing Zone architecture serves as an excellent starting point while still requiring customization for individual business requirements.

    MICROSOFT CLOUD ADOPTION FRAMEWORK AND WELL-ARCHITECTED DESIGN
    The Microsoft Cloud Adoption Framework offers far more than technical guidance. It provides a comprehensive roadmap covering business strategy, governance, security, organizational change, operations, and cloud architecture. Jev discusses how organizations should gradually introduce the framework without overwhelming teams, allowing architects, operations teams, and security specialists to focus on the areas most relevant to their roles. The episode also explores how the Azure Well-Architected Framework complements Cloud Adoption Framework by helping architects design highly available, secure, reliable, performant, and cost-optimized cloud workloads.

    AUTOMATION, INFRASTRUCTURE AS CODE, AND MODERN GOVERNANCE
    Automation sits at the center of every successful Azure platform. Infrastructure as Code enables organizations to deploy consistent environments, improve compliance, reduce configuration drift, and implement security earlier in the deployment lifecycle. Jev explains how Bicep, Terraform, Azure Verified Modules, Azure Policy, and automated guardrails allow platform teams to create repeatable cloud environments while reducing operational risk. Listeners also learn how proactive governance replaces traditional reactive operations through policy enforcement, remediation, monitoring, and standardized deployment practices.

    BUILDING SELF-SERVICE PLATFORMS DEVELOPERS LOVE
    Platform Engineering is ultimately about creating internal platforms that enable development teams to deliver business value faster. Instead of becoming operational bottlenecks, platform teams should provide self-service capabilities, reusable templates, deployment pipelines, standardized environments, and automated security controls. Jev explains why developers should be viewed as customers of the platform and how organizations can balance flexibility with governance by providing clear guardrails rather than unnecessary restrictions. The discussion also covers GitHub, Azure DevOps, Internal Developer Platforms, and why successful platforms focus on enabling developers instead of competing with the Azure Portal.

    AI, CLOUD OPERATIONS, AND THE FUTURE OF ENTERPRISE AZURE
    Artificial Intelligence is rapidly changing the daily work of cloud engineers and platform architects. Jev shares how GitHub Copilot accelerates Infrastructure as Code development, improves productivity, and assists experienced engineers while emphasizing the importance of architectural knowledge and critical thinking. The conversation concludes with practical advice on cloud adoption, governance, platform engineering, Azure security, automation, developer experience, and why organizations should automate repetitive tasks while allowing engineers to focus on solving complex business challenges. The key takeaway is simple yet powerful: automate the boring work so people can concentrate on innovation.

    Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
    続きを読む 一部表示
    1 時間 3 分
  • Microsoft Entra Verified ID - Simply Explained

    Microsoft Entra Verified ID - Simply Explained
    2026/08/05
    Modern identity security extends far beyond passwords and multi-factor authentication. While Microsoft Entra ID, passkeys, and MFA help verify that someone controls a sign-in method, they cannot prove important real-world facts such as employment status, completed security training, professional certifications, contractor relationships, or verified identity during account recovery. In this Microsoft Knowledge Nuggets episode, Mirko Peters explains Microsoft Entra Verified ID in plain English, showing how organizations can replace manual document verification with secure, privacy-friendly digital credentials that improve trust while reducing administrative effort.UNDERSTANDING MICROSOFT ENTRA VERIFIED IDMicrosoft Entra Verified ID enables organizations to issue, store, and verify digital credentials based on open standards for decentralized identity. Instead of emailing PDFs, screenshots, certificates, or identity documents, trusted organizations issue digitally signed credentials that individuals securely store inside the Microsoft Authenticator app. These credentials contain verified claims such as employee status, completed training, professional licenses, student enrollment, or supplier relationships. When another organization requests proof, users decide whether to share the required information while the verifier can validate the credential's authenticity, issuer, expiration date, and revocation status without relying on manual phone calls or email confirmations.ISSUERS, HOLDERS, AND VERIFIERS: THE VERIFIED ID MODELEvery Microsoft Entra Verified ID solution follows a simple three-party trust model. The issuer creates and digitally signs the credential after validating information from trusted business systems. The holder receives and securely stores the credential in their digital wallet within Microsoft Authenticator. The verifier requests specific claims to support a business decision such as granting access, approving onboarding, confirming qualifications, or validating identity during sensitive operations. This model significantly reduces document handling, minimizes unnecessary sharing of personal information, and creates a more secure verification process that scales across organizations.FACE CHECK AND HIGH-ASSURANCE IDENTITY VERIFICATIONFor higher-risk scenarios, Microsoft Entra Verified ID introduces Face Check to strengthen identity verification. Face Check compares a live selfie with the photo stored inside the verified credential, helping organizations confirm that the individual presenting the credential is the legitimate credential holder. The episode explores practical use cases including remote employee onboarding, privileged account recovery, contractor verification, privileged access requests, and high-security administrative operations. Combined with Microsoft Entra ID, Face Check provides stronger protection against impersonation attacks, deepfakes, stolen devices, and social engineering while supporting Zero Trust identity principles.PRACTICAL MICROSOFT 365 USE CASES FOR VERIFIED IDMicrosoft Entra Verified ID integrates naturally with Microsoft 365 identity and governance scenarios. Organizations can automate remote onboarding, simplify secure account recovery, validate contractor relationships, confirm training completion before granting access to sensitive projects, and verify qualifications without exchanging physical documents. Combined with Microsoft Entra Access Packages, Microsoft Teams, SharePoint Online, enterprise applications, and Microsoft Entra role assignments, Verified ID enables organizations to make access decisions based on trusted business facts instead of manual document reviews. This reduces administrative overhead while improving both security and user privacy.BUILDING A TRUSTED DIGITAL IDENTITY STRATEGYSuccessfully implementing Microsoft Entra Verified ID requires careful planning around credential issuance, trusted issuers, claim definitions, expiration policies, revocation processes, governance, and user experience. Organizations should begin with a single business scenario that already involves manual identity verification, establish clear trust relationships, define credential lifecycles, and gradually expand their implementation. As digital identity continues evolving, Microsoft Entra Verified ID provides a scalable foundation for privacy-preserving verification that complements Microsoft Entra ID, MFA, passkeys, and Zero Trust architecture while helping organizations modernize identity proofing across employees, partners, contractors, students, and customers.Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
    続きを読む 一部表示
    18 分
  • Windows 365 Link - Simply Explained

    Windows 365 Link - Simply Explained
    2026/08/04
    Windows 365 Link is Microsoft's purpose-built access device for Windows 365 Cloud PCs, designed to deliver a secure, simplified desktop experience without storing applications, files, or user profiles locally. Rather than functioning as a traditional Windows PC, Windows 365 Link acts as a secure gateway that connects employees directly to their personal Cloud PC running in Microsoft's cloud. In this Microsoft Knowledge Nuggets episode, Mirko Peters explains Windows 365 Link in plain English, covering its architecture, hardware, licensing, identity management, security features, and the business scenarios where it provides the greatest value. Whether you're an IT administrator, Microsoft consultant, solution architect, or business decision-maker, this episode explains how Microsoft's cloud-first desktop strategy is reshaping modern workplace computing.UNDERSTANDING THE DIFFERENCE BETWEEN WINDOWS 365 LINK AND WINDOWS 365 CLOUD PCSOne of the biggest misconceptions is that Windows 365 Link is simply another compact Windows computer. In reality, the Link device and the Cloud PC perform two completely different roles. The Link hardware serves as the secure connection point, while the actual Windows operating system, installed applications, user settings, documents, and workloads execute inside a Windows 365 Cloud PC hosted in Microsoft Azure. This separation allows employees to move between desks, offices, and shared workspaces while maintaining the same personalized Windows experience every time they sign in with their Microsoft Entra ID account.HOW MICROSOFT DELIVERS A SECURE CLOUD DESKTOP EXPERIENCESecurity sits at the heart of the Windows 365 Link architecture. The device is intentionally designed with a minimal local footprint, eliminating traditional risks associated with locally stored files, installed applications, administrator accounts, and unmanaged software. The episode explores how Microsoft Entra ID, Microsoft Intune, Trusted Platform Module (TPM), Secure Boot, BitLocker encryption, Microsoft Defender, and strict application controls work together to protect both the access device and the cloud-hosted desktop environment. Combined with Zero Trust identity verification and centralized device management, organizations gain a highly secure endpoint while significantly reducing operational complexity.MODERN DEVICE MANAGEMENT WITH MICROSOFT INTUNEWindows 365 Link simplifies endpoint management by separating device administration from user computing. Microsoft Intune manages the Link hardware by enforcing security policies, deploying updates, monitoring compliance, and maintaining device configuration, while Windows 365 manages the Cloud PC assigned to each employee. This dual-management approach enables organizations to support hot-desking, shared workspaces, contact centers, healthcare environments, training facilities, retail operations, and frontline workers without maintaining a unique Windows installation on every physical device. The result is simplified lifecycle management, faster hardware replacement, and greater operational consistency across enterprise environments.WHO SHOULD DEPLOY WINDOWS 365 LINK?Windows 365 Link is best suited for organizations that have already standardized on Windows 365 Cloud PCs and Microsoft Entra ID. Shared desks, shift workers, call centers, reception areas, branch offices, training rooms, and secure office environments benefit most from the device's cloud-first design. However, the episode also explains where traditional laptops remain the better option. Mobile employees, field workers, developers requiring local software installations, creative professionals using high-performance applications, and users who frequently work offline continue to benefit from full Windows devices. Understanding these deployment scenarios helps organizations choose the right endpoint strategy for each user persona.BUILDING THE FUTURE OF CLOUD-FIRST END USER COMPUTINGWindows 365 Link represents Microsoft's long-term vision for cloud-based desktop computing. Instead of managing complex local devices, organizations can centralize Windows environments in the cloud while providing employees with secure, purpose-built access hardware. Combined with Windows 365 Cloud PCs, Microsoft Intune, Microsoft Entra ID, Microsoft Teams optimization, and modern endpoint management, Windows 365 Link enables businesses to simplify IT operations, improve security, support flexible workplaces, and prepare for the next generation of enterprise computing. For organizations embracing cloud-first infrastructure, Windows 365 Link provides a practical foundation for scalable, secure, and highly manageable digital workspaces.Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
    続きを読む 一部表示
    19 分
  • Building Modern Microsoft 365 Solutions with SharePoint Framework, Microsoft Graph, PnPjs & Great User Experiences with Julie Turner [MVP]

    Building Modern Microsoft 365 Solutions with SharePoint Framework, Microsoft Graph, PnPjs & Great User Experiences with Julie Turner [MVP]
    2026/08/04
    Modern Microsoft 365 development is about far more than writing code. Organizations expect solutions that integrate seamlessly across SharePoint, Microsoft Teams, Microsoft Graph, Azure, and Microsoft 365 while remaining scalable, secure, maintainable, and ready for future innovation. In this episode of M365.FM, Microsoft MVP Julie Turner shares decades of real-world experience designing enterprise-grade Microsoft 365 solutions. From SharePoint Framework (SPFx) and Microsoft Graph to PnPjs, open-source development, UX design, and AI-assisted coding, this conversation provides practical guidance for developers, solution architects, consultants, and technical decision makers building on the Microsoft platform.

    WHY MICROSOFT 365 EXTENSIBILITY MATTERS MORE THAN EVER
    Microsoft 365 has evolved into a powerful business platform that goes far beyond email and collaboration. Julie explains how extensibility enables organizations to transform Microsoft 365 into a tailored business platform by integrating external systems, automating business processes, extending SharePoint and Teams, and creating custom user experiences. Rather than replacing standard Microsoft functionality, modern development focuses on extending it through supported APIs, frameworks, and services that remain compatible with Microsoft's continuous cloud updates.

    SHAREPOINT FRAMEWORK AS THE FOUNDATION OF MODERN DEVELOPMENT
    SharePoint Framework has become the standard for building supported client-side solutions across Microsoft 365. Julie explains why SPFx remains the preferred development model for SharePoint Online, Microsoft Teams, and Microsoft 365 experiences. The discussion covers hosted deployment, simplified maintenance, supported customization, reusable components, and how developers can build scalable enterprise applications without maintaining complex infrastructure. The episode also highlights the best learning resources, Microsoft Learn content, and the extensive Patterns and Practices (PnP) community for developers getting started with SharePoint Framework.

    MICROSOFT GRAPH, PNPJS, AND THE FUTURE OF ENTERPRISE APIS
    Microsoft Graph has become the central gateway into Microsoft 365, but understanding when to use Graph versus native SharePoint REST APIs remains critical. Julie discusses the strengths and current limitations of Microsoft Graph, endpoint maturity, authentication, permissions, performance considerations, and enterprise security. She also explains how PnPjs dramatically simplifies development by eliminating repetitive boilerplate code, providing fluent APIs, simplifying authentication, retry logic, error handling, and API consumption. Listeners also gain insight into the future roadmap of PnPjs Version 5 and the importance of semantic versioning in large open-source projects.

    DESIGNING USER EXPERIENCES THAT PEOPLE ACTUALLY ENJOY USING
    Technology alone does not create successful solutions. Great user experience often determines whether employees embrace or avoid enterprise software. Julie shares practical examples from real customer projects, explaining how thoughtful UX design improves productivity, reduces friction, and increases adoption. Whether building mobile applications for field workers, internal business applications, or Microsoft 365 solutions, developers should focus on simplicity, responsiveness, accessibility, and minimizing unnecessary user interaction. Small UX decisions can have enormous impacts on employee satisfaction and business efficiency.

    OPEN SOURCE, AI, AND THE FUTURE OF MICROSOFT DEVELOPMENT
    The conversation concludes with an honest discussion about open-source software, AI-assisted development, GitHub Copilot, Claude Code, Microsoft Copilot, and the future relationship between low-code and pro-code development. Julie explains why AI should enhance—not replace—developer expertise, how experienced developers can use AI as a collaborative assistant rather than an automated replacement, and why logical thinking and software architecture remain essential skills. The episode finishes with rapid-fire questions covering favorite developer tools, coding preferences, Microsoft events, future improvements for Microsoft Graph, and practical advice for developers who want to start building modern Microsoft 365 solutions today.

    Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
    続きを読む 一部表示
    1 時間
  • Azure Local - Simply Explained

    Azure Local - Simply Explained
    2026/08/04
    As organizations rapidly adopt generative AI, the number of AI-powered applications, copilots, intelligent agents, and automation workflows continues to grow. What often begins as a single chatbot quickly expands into dozens of AI services connected to different models, APIs, business systems, and external providers. Without centralized governance, organizations face increasing security risks, inconsistent access controls, rising token costs, and limited visibility into AI usage. In this Microsoft Knowledge Nuggets episode, Mirko Peters explains Microsoft AI Gateway in plain English, demonstrating how Azure API Management provides a secure front door for enterprise AI traffic while simplifying governance, monitoring, and operational management.UNDERSTANDING MICROSOFT AI GATEWAY AND AZURE API MANAGEMENTMicrosoft AI Gateway extends Azure API Management by introducing centralized control over AI traffic, model endpoints, intelligent agents, Model Context Protocol (MCP) tools, Agent-to-Agent (A2A) communication, and existing business APIs. Rather than allowing every application to communicate directly with different AI providers, organizations create a single managed entry point where authentication, authorization, routing, rate limiting, logging, and security policies are consistently enforced. This separation allows development teams to focus on building intelligent business applications while platform teams maintain governance, compliance, and operational standards across the entire AI landscape.ROUTING AI REQUESTS ACROSS MULTIPLE MODELS AND PROVIDERSOne of the greatest advantages of Microsoft AI Gateway is the ability to separate applications from individual AI model deployments. Instead of hardcoding connections to specific providers, applications communicate with a stable endpoint while the gateway intelligently routes requests to Azure OpenAI, Microsoft Foundry, Anthropic, Google Gemini, Amazon Bedrock, or other approved model providers. Organizations can balance workloads across multiple regions, optimize performance, reduce operational risk, implement failover strategies, and migrate between models without requiring application developers to rewrite existing integrations. This flexible architecture enables enterprises to adapt quickly as AI technology continues evolving.GOVERNING AGENTS, TOOLS, AND BUSINESS APISModern AI extends far beyond simple chatbots. Intelligent agents increasingly interact with HR systems, finance applications, customer records, enterprise databases, and internal APIs. Microsoft AI Gateway provides centralized governance for Model Context Protocol (MCP) servers, Agent-to-Agent communication, and business APIs by enforcing identity, authorization, content safety, and Zero Trust principles. Combined with Microsoft Entra ID managed identities, organizations can ensure every AI agent receives only the minimum permissions required to perform its assigned task. This dramatically reduces the risk of unauthorized data access while creating complete visibility into every AI-driven action.MANAGING TOKEN COSTS, PERFORMANCE, AND AI OBSERVABILITYUnlike traditional software licensing, generative AI introduces variable consumption costs based on token usage. Microsoft AI Gateway helps organizations control these expenses through request throttling, quotas, token budgets, semantic caching, traffic prioritization, and detailed monitoring. Every AI request can be logged with information about the calling application, selected model, token consumption, response status, latency, and tool execution. This observability enables platform teams to identify inefficient prompts, detect abnormal consumption patterns, optimize model selection, and allocate AI costs across departments while ensuring mission-critical business workloads always receive sufficient capacity.BUILDING A SECURE FOUNDATION FOR SCALABLE ENTERPRISE AIMicrosoft AI Gateway is not another AI model or agent builder. Instead, it provides the governance layer that allows organizations to safely scale enterprise AI initiatives. By combining Azure API Management, Microsoft Entra ID, Azure AI Foundry, MCP, A2A communication, API Center, content safety, centralized policies, and comprehensive monitoring, businesses gain a unified architecture capable of supporting future AI innovation without sacrificing security or compliance. Organizations beginning their AI journey should start with a single managed workload, establish governance from the beginning, and gradually expand toward a standardized enterprise AI platform that remains secure, observable, and cost-efficient.Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
    続きを読む 一部表示
    17 分
  • Microsoft AI Gateway - Simply Explained

    Microsoft AI Gateway - Simply Explained
    2026/08/03
    As organizations rapidly adopt generative AI, the number of AI-powered applications, copilots, intelligent agents, and automation workflows continues to grow. What often begins as a single chatbot quickly expands into dozens of AI services connected to different models, APIs, business systems, and external providers. Without centralized governance, organizations face increasing security risks, inconsistent access controls, rising token costs, and limited visibility into AI usage. In this Microsoft Knowledge Nuggets episode, Mirko Peters explains Microsoft AI Gateway in plain English, demonstrating how Azure API Management provides a secure front door for enterprise AI traffic while simplifying governance, monitoring, and operational management.UNDERSTANDING MICROSOFT AI GATEWAY AND AZURE API MANAGEMENTMicrosoft AI Gateway extends Azure API Management by introducing centralized control over AI traffic, model endpoints, intelligent agents, Model Context Protocol (MCP) tools, Agent-to-Agent (A2A) communication, and existing business APIs. Rather than allowing every application to communicate directly with different AI providers, organizations create a single managed entry point where authentication, authorization, routing, rate limiting, logging, and security policies are consistently enforced. This separation allows development teams to focus on building intelligent business applications while platform teams maintain governance, compliance, and operational standards across the entire AI landscape.ROUTING AI REQUESTS ACROSS MULTIPLE MODELS AND PROVIDERSOne of the greatest advantages of Microsoft AI Gateway is the ability to separate applications from individual AI model deployments. Instead of hardcoding connections to specific providers, applications communicate with a stable endpoint while the gateway intelligently routes requests to Azure OpenAI, Microsoft Foundry, Anthropic, Google Gemini, Amazon Bedrock, or other approved model providers. Organizations can balance workloads across multiple regions, optimize performance, reduce operational risk, implement failover strategies, and migrate between models without requiring application developers to rewrite existing integrations. This flexible architecture enables enterprises to adapt quickly as AI technology continues evolving.GOVERNING AGENTS, TOOLS, AND BUSINESS APISModern AI extends far beyond simple chatbots. Intelligent agents increasingly interact with HR systems, finance applications, customer records, enterprise databases, and internal APIs. Microsoft AI Gateway provides centralized governance for Model Context Protocol (MCP) servers, Agent-to-Agent communication, and business APIs by enforcing identity, authorization, content safety, and Zero Trust principles. Combined with Microsoft Entra ID managed identities, organizations can ensure every AI agent receives only the minimum permissions required to perform its assigned task. This dramatically reduces the risk of unauthorized data access while creating complete visibility into every AI-driven action.MANAGING TOKEN COSTS, PERFORMANCE, AND AI OBSERVABILITYUnlike traditional software licensing, generative AI introduces variable consumption costs based on token usage. Microsoft AI Gateway helps organizations control these expenses through request throttling, quotas, token budgets, semantic caching, traffic prioritization, and detailed monitoring. Every AI request can be logged with information about the calling application, selected model, token consumption, response status, latency, and tool execution. This observability enables platform teams to identify inefficient prompts, detect abnormal consumption patterns, optimize model selection, and allocate AI costs across departments while ensuring mission-critical business workloads always receive sufficient capacity.BUILDING A SECURE FOUNDATION FOR SCALABLE ENTERPRISE AIMicrosoft AI Gateway is not another AI model or agent builder. Instead, it provides the governance layer that allows organizations to safely scale enterprise AI initiatives. By combining Azure API Management, Microsoft Entra ID, Azure AI Foundry, MCP, A2A communication, API Center, content safety, centralized policies, and comprehensive monitoring, businesses gain a unified architecture capable of supporting future AI innovation without sacrificing security or compliance. Organizations beginning their AI journey should start with a single managed workload, establish governance from the beginning, and gradually expand toward a standardized enterprise AI platform that remains secure, observable, and cost-efficient.Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
    続きを読む 一部表示
    18 分
  • Microsoft Power Fx - Simply Explained

    Microsoft Power Fx - Simply Explained
    2026/08/03
    Power Fx is the formula language that powers Microsoft Power Apps and an increasing number of experiences across the Microsoft Power Platform. For anyone familiar with Excel, Power Fx provides a natural transition into app development by using familiar formula concepts instead of traditional programming languages. In this episode of Microsoft Knowledge Nuggets on M365.FM, Mirko Peters explains Power Fx in plain English, showing how formulas can control text, colors, visibility, calculations, navigation, and business logic inside modern business applications. Whether you're an Excel user, Power Apps beginner, citizen developer, or IT professional, this episode demonstrates how Power Fx enables low-code application development without requiring years of programming experience.

    FROM EXCEL FORMULAS TO BUSINESS APPLICATIONS
    One of the greatest strengths of Power Fx is its familiar spreadsheet mindset. Instead of writing complex code, developers create formulas that respond automatically as users interact with an application. The episode explains how Excel formulas translate into Power Apps properties, allowing labels, buttons, text boxes, galleries, and forms to update dynamically based on user input. Rather than thinking about individual spreadsheet cells, Power Apps developers work with controls and properties that continuously respond to changing business data, creating interactive applications that feel intelligent while remaining easy to maintain.

    USING POWER FX TO CREATE DYNAMIC USER EXPERIENCES
    Business applications are built around rules, and Power Fx provides the logic behind every interaction. The discussion explores properties such as Text, Visible, Color, and OnSelect, demonstrating how formulas determine what users see and what happens when they interact with buttons, forms, or screens. Listeners learn how applications automatically show or hide controls, validate information, display notifications, navigate between screens, and provide immediate feedback without requiring traditional software development. The result is a responsive user experience that adapts naturally to business processes.

    CONNECTING POWER APPS TO BUSINESS DATA
    Modern applications rarely exist without data. This episode explains how Power Fx works with business information stored in SharePoint, Microsoft Dataverse, SQL Server, Excel, and other supported data sources. Core functions such as Filter, Sort, LookUp, and Patch allow developers to retrieve, organize, search, create, and update business records while keeping applications responsive and easy to understand. The episode also introduces the concepts of tables, records, columns, and galleries, helping beginners understand how business data flows through a Power Apps solution.

    VARIABLES, COLLECTIONS, AND REUSABLE BUSINESS LOGIC
    As applications grow, developers need efficient ways to manage state and reuse business rules. Mirko explains how variables temporarily store information during a user's session, while collections manage groups of records before saving them to permanent storage. The discussion also covers reusable Power Fx functions that prevent duplicated logic and simplify long-term maintenance. By organizing formulas properly, developers can build scalable business applications that remain easier to troubleshoot, update, and extend as organizational requirements evolve.

    WHY POWER FX IS THE FUTURE OF LOW-CODE DEVELOPMENT
    Microsoft continues expanding Power Fx across the Power Platform, making it a core skill for citizen developers, business analysts, consultants, and enterprise application builders. Rather than replacing professional developers, Power Fx enables organizations to build business applications faster while allowing experienced developers to focus on more complex scenarios. The episode concludes with practical advice for beginners, encouraging listeners to start with simple formulas, build one feature at a time, and gradually develop confidence using Power Fx to automate business processes, improve productivity, and transform ideas into working applications.

    Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
    続きを読む 一部表示
    18 分