Azure AI Foundry agents, Threads, Runs, Run Steps, observability and governance – this episode is for people searching “Azure AI Foundry agents explained”, “Threads Runs Run Steps logging”, “enterprise AI observability” or “how to govern AI agents in Azure” and wanting a concrete mental model instead of marketing slides. We start with the part almost nobody tells you: when you deploy an AI in Azure AI Foundry, you’re not just spinning up one big model – you’re dropping it into a managed runtime where every message, tool call and run step is logged and traced, turning experiments into something auditable and enterprise‑ready.

From there, we zoom in on the squad leader: the Azure AI agent built from three core gears – Model, Instructions and Tools. You’ll hear why this triad matters so much for reproducibility and control, how “just a chat endpoint” is like sending a captain into the field without orders or gear, and how Foundry lets you mix and match models (GPT‑4o, leaner models, or even others) while keeping a stable, governed mission frame around them. We use battlefield and gaming analogies to make the architecture intuitive: the model as the brain, instructions as mission orders, and tools as specialized equipment wired into your enterprise systems and APIs.

Then we move to Threads – your battlefront log. Unlike disposable chat windows, Threads are persistent conversation sessions that store structured messages, including text, images, files and generated code, with roles and timestamps. You’ll see why that gives you both continuity for the agent and a durable ledger for compliance, debugging and audits, and how it compares to systems where conversations vanish and you’re left with screenshots and guesswork when regulators or stakeholders ask “what exactly happened here?”.

Then we move to Threads – your battlefront log. Unlike disposable chat windows, Threads are persistent conversation sessions that store structured messages, including text, images, files and generated code, with roles and timestamps. You’ll see why that gives you both continuity for the agent and a durable ledger for compliance, debugging and audits, and how it compares to systems where conversations vanish and you’re left with screenshots and guesswork when regulators or stakeholders ask “what exactly happened here?”.Finally, we dissect Runs and Run Steps – where missions actually fire and where observability becomes real. Runs take the context in a Thread and execute it through the agent, with explicit statuses and a full breakdown of each action. Run Steps give you chess‑notation style traceability over the execution path: which tools were called, what code ran, what messages were produced and in which order, so you can debug failures, prove compliance and build trust in how your “agent army” behaves across tools, data and teams. By the end, you’ll see how Azure AI Foundry turns AI from a loose cannon into a disciplined, logged and governable digital squad you can actually put in front of real workflows.

WHAT YOU WILL LEARN

• How Azure AI Foundry’s managed runtime logs messages, tool calls and run steps for auditability.
• Why real Azure AI agents are built from Model, Instructions and Tools, not just a prompt.
• How to think about your main agent as a “squad leader” coordinating tools and data sources.
• What Threads are, how they persist conversations and why they matter for compliance.
• How Runs kick off execution and how Run statuses help monitor live workloads.
• Why Run Steps are essential for observability, debugging and structured traceability.
• The risks of running “just chat” without logs, and how Foundry closes that gap.
• Practical implications for governance, guardrails and enterprise AI readiness in Azure.

THE CORE INSIGHT

The core insight of this episode is that the power of Azure AI Foundry isn’t just the model catalog – it’s the way agents, Threads, Runs and Run Steps combine into a disciplined, observable system you can actually govern. When you treat your Azure AI agent as a structured squad leader with clear orders, tools and a full mission log, you move from ad‑hoc text generation to a tracked, auditable “agent army” that enterprises can trust in real workflows.

WHO THIS IS FOR

• Platform and engineering teams building on Azure AI Foundry.
• Architects and governance leads defining observability and logging for AI systems.
• Product and AI leaders designing multi‑tool agents for real business workflows.
• Compliance, risk and audit teams who need traceability for AI behavior.
• Developers moving from simple chat APIs to production‑grade agent architectures.

ABOUT THE HOST

Mirko Peters is a Microsoft 365 consultant and host of M365.FM, where he explores modern work, AI and productivity with a focus on how systems behave in real organizations, not just lab demos. He helps teams translate concepts like agents, observability, governance and managed runtimes into practical Azure designs that both IT and business stakeholders can trust.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

Modernizing your teamwork tools is important today. The SharePoint Server Subscription Edition gives big benefits. It can change how your team works together. By using this platform, you can boost productivity. This happens through easier workflows and better user engagement. Reports show clear productivity gains. These include more active users and quicker workflows. This change not only makes finding information easier. It also helps your organization work together better.Key Takeaways* Updating teamwork tools with SharePoint Server Subscription Edition helps people work better together.* Use best practices for moving, like setting clear goals and keeping important data, to make the change easy.* Find and change old features to make things better for users and get the most from the new system.* Use better user interface designs and Microsoft 365 connections to make things easier and faster.* Think about the benefits of on-premise solutions and mixed setups to fit your organization’s needs.SharePoint Migration StrategiesMoving to the SharePoint Server Subscription Edition can feel hard. But using best practices can help a lot. Here are some important strategies to think about during your move.Content Migration Best PracticesWhen you move content to SharePoint, remember these best practices:* Define the Scope of Migration: Clearly say what content you need to move. This helps avoid confusion and makes sure you only transfer important files.* Plan for Large Data Volumes: If you have a lot of data, get ready for possible stress on your network. This can help stop errors and downtime during the move.* Retain Metadata and Permissions: Make sure to move metadata and permissions correctly. Not doing this can cause confusion and security problems.* Use Reliable Tools: Think about using tools like the SharePoint Migration Tool or Azure Data Factory. These tools help keep metadata and permissions safe during the move.* Anticipate User Resistance: After the move, users might not know how to use the new interface. Giving training resources can help them adjust.Common problems organizations face during SharePoint migration include:* Incompatibility between systems, which can cause broken links or data loss.* Managing large data volumes that can make migration take longer.* User resistance to change, which can slow down using the new platform.By solving these problems early, you can make a better migration plan.Handling CustomizationsCustomizations can make your SharePoint experience better, but they need careful handling during the move. Here are some best practices for managing customizations:* Create a Comprehensive Migration Checklist: This checklist should list all custom workflows and web parts. It makes sure nothing important gets missed.* Understand Compatibility: Know that some customizations from older SharePoint versions may not work in the SharePoint Server Subscription Edition. You might need to change or replace some features.* Replace Sandboxed Solutions: If you used sandboxed solutions before, find new features. These solutions will not work after the move.* Test Customizations: Before fully moving, test your customizations in a safe environment. This helps find any problems that might happen.Moving to the SharePoint Server Subscription Edition is a chance to update your document management and teamwork processes. By following these strategies, you can make the transition easier and help your organization succeed.Addressing Legacy FeaturesAs organizations move to the SharePoint Server Subscription Edition, you need to deal with old features from past SharePoint versions. Finding these features is important for a smooth move. It helps your team use modern tools well.Identifying Outdated FeaturesMany old features in SharePoint do not fit today’s users. Here are some outdated features you might find:* Access Services 2010* Access Services 2013* Aggregated Newsfeed* Custom Help* Groove.exe (Old OneDrive for Business sync app)* InfoPath Services* Lists Web Service* Machine Translations* Variations* PerformancePoint ServicesKnowing these outdated features helps you plan to replace them. This way, your organization won’t depend on features that are no longer supported.Transitioning to Modern AlternativesAfter you find outdated features, you can look for modern options in the SharePoint Server Subscription Edition. Switching to these options improves teamwork and user experience. Below is a table showing old features and their modern replacements:To make the switch smoothly, follow these steps:* Assess your current infrastructure: Check your existing SharePoint setup to find compatibility problems and decide what to move first.* Plan your migration: Create a clear migration plan that includes preparing data, a step-by-step approach, user training, and testing.* Execute the migration: Use the right tools and methods, including Microsoft tools and third-party options, to carry out the move effectively.By dealing with old features and switching to modern options, you can help your organization get the most from the SharePoint Server Subscription Edition. This forward-thinking approach boosts teamwork and gets your team ready for future tech improvements.Enhancing User ExperienceThe SharePoint Server Subscription Edition has many improvements for users. These changes help you use the platform more easily.User Interface ImprovementsYou will see some important features that make your experience better:These updates create a friendlier environment. You can find what you need quickly. The focus on accessibility helps everyone use the platform well.Integration with Microsoft 365Connecting SharePoint with Microsoft 365 tools makes working together better. Here are some tools that work well with SharePoint:This connection offers many benefits:* Better efficiency by making data easy to access.* Improved teamwork by allowing direct work on documents in familiar apps.* Stronger data security with centralized control of sensitive information.With these tools, you can work together in real-time. You can also manage documents better. This leads to higher productivity and smoother workflows.However, some users might struggle with the new interface. They may find the layout strange or hard to understand. Providing training resources can help them learn how to use the new features well.By using these user interface improvements and integrations, you can get the most out of the SharePoint Server Subscription Edition. This updated platform meets your teamwork needs while being easy to use.On-Premise vs. Online CollaborationWhen you think about collaboration tools, you have to choose between on-premise and online options. Each choice has its own benefits. Knowing these benefits can help you decide what’s best for your organization.Benefits of On-Premise SolutionsOn-premise solutions have some important advantages over online ones. Here’s a list of the main benefits:Besides these benefits, on-premise solutions also offer strong security and compliance advantages:* You control how security and data management are set up.* You can create compliance policies that fit your internal or industry rules.* Your data stays private since it is stored on-site.These reasons make on-premise solutions attractive, especially for organizations that care about data security and compliance.Hybrid Integration with Microsoft 365The SharePoint Server Subscription Edition allows hybrid integration with Microsoft 365. This means you can enjoy the best of both on-premise and cloud solutions. Here’s how it works:To create a hybrid setup, you must sync your on-premises Active Directory user accounts with Microsoft 365. You can pick between syncing directories with password sync or using single sign-on (SSO). You can also set up password sync as a backup for SSO.With hybrid search in SharePoint, you get a combined search experience. This feature brings together results from both on-premises and Microsoft 365 content into one search index. Users can see and rank results from all sources in one spot, making their searches more efficient and relevant.As more organizations use hybrid models, it’s important t

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack

Active Directory security, attack paths, credential hygiene and identity hardening – this episode is for people searching “Active Directory security best practices”, “AD attack paths”, “domain admin blast radius”, “Kerberos abuse”, “golden ticket attack” or “AD CS / PKI hardening” and wanting a concrete, modern defensive playbook. We treat Active Directory as the crown jewel that attackers hunt: if they own AD, they own your organization, which is why paths like DCSync, pass‑the‑hash, lateral movement and privilege escalation via service accounts are so heavily targeted.

We walk through how misconfigured certificate templates in AD CS, weak admin tiering, and poor credential hygiene quietly create ESC1–ESC8‑style paths straight to domain dominance. You’ll hear how attackers chain small misconfigurations (service accounts, PKI, Kerberos, LSASS, delegation) into a full compromise, and how techniques like golden tickets or DCSync are often just the final step of a long‑standing blast radius problem around domain admins and privileged groups.

Then we move into defense and hardening. We explain how to map and reduce attack paths, shrink domain admin blast radius, improve credential hygiene, protect LSASS, harden AD CS and PKI, and use tiering models effectively instead of just drawing them on a slide. The goal is to give you a realistic, prioritized roadmap: which fixes reduce the most risk fastest, where to start if everything feels on fire, and how to communicate these identity security issues to stakeholders who don’t live in Kerberos every day.

WHAT YOU WILL LEARN

• Why Active Directory is the crown jewel and prime target for attackers.
• How attack paths form through misconfigurations, weak tiering and poor credential hygiene.
• What techniques like DCSync, golden tickets and pass‑the‑hash actually enable in practice.
• How AD CS, PKI and vulnerable certificate templates (ESC1–ESC8) open privilege escalation paths.
• How to reduce domain admin blast radius and harden privileged access.
• Practical steps to protect LSASS, service accounts and Kerberos from common abuse patterns.
• How to use admin tiering models in a way that actually changes attacker options.
• A pragmatic starting roadmap for AD hardening even in messy, legacy environments.

THE CORE INSIGHT

The core insight of this episode is that most organizations don’t lose Active Directory in one dramatic event – they lose it through years of small identity and PKI decisions that quietly create rich attack paths. By treating AD as a true crown jewel, mapping and shrinking attack paths, and hardening tiering, PKI and credentials systematically, you can dramatically raise the cost for attackers and take back control of your identity core.

WHO THIS IS FOR

• Identity and security engineers responsible for Active Directory.
• Security architects and blue teamers focused on lateral movement and privilege escalation.
• IT admins who inherited a messy AD, PKI and tiering setup and need a way forward.
• CISOs and security leaders prioritizing identity security and blast radius reduction.
• Red teamers and defenders who want a shared language for AD attack paths and fixes.

ABOUT THE HOST

Mirko Peters is a Microsoft 365 consultant and host of M365.FM, where he explores modern work, security and productivity with a strong focus on identity, Active Directory and cloud‑connected environments. He helps teams translate complex identity and PKI topics into practical hardening steps that both security and infrastructure teams can execute together.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

In today’s digital world, knowing Microsoft 365 Development is very important for organizations. You have more demands for safe and flexible solutions that can change with business needs. Recent reports say that organizations with many global admin accounts are more likely to have account problems. Also, more than half of organizations have many apps with large permissions. This shows the need for good management. By focusing on safety and flexibility, you can build strong solutions. These solutions will not only solve current problems but also help your organization succeed in the long run.Key Takeaways* Focus on security by using the least privilege rule. Limit user permissions to lower the risk of unauthorized access.* Use Microsoft 365 tools like Power Platform and Microsoft Graph. These tools help create custom apps that boost productivity.* Plan for growth by building strong systems. Regularly check app performance to meet increasing user needs.* Set up a good governance plan. This should include clear rules, regular training, and checking for compliance to keep a safe environment.* Keep up with Microsoft 365 changes. Test new features in a safe space and adjust your apps as needed.Microsoft 365 OverviewMicrosoft 365 is a strong platform for development. It helps you create new solutions for your organization. It has many tools and services. These tools help you build apps, automate tasks, and work better together. Knowing the main parts of Microsoft 365 is important for any developer. This knowledge helps you use its full power.Key ComponentsHere are some main parts of Microsoft 365 that you can use to build business solutions:These parts help you make solutions that fit your organization’s needs. By using these tools, you can boost productivity and make processes smoother.Development ToolsMicrosoft 365 has many development tools. These tools help you create and manage applications easily. Some of these tools are:* Microsoft Graph: This unified API lets you access data across Microsoft 365 services. It makes it easier to connect and manage your apps.* Power Platform: This set includes Power Apps, Power Automate, and Power BI. It helps you build apps, automate tasks, and analyze data without much coding.* SharePoint Framework (SPFx): This framework helps you create modern web parts for SharePoint and Teams. It improves user experience.By learning these tools, you can work well with the Microsoft 365 system. You can create solutions that are safe and can grow with your needs.Designing Secure SolutionsIn Microsoft 365 Development, making secure solutions is very important. You need to focus on security at every step of your development. This helps protect sensitive data and builds trust with users. Here are some key security best practices to follow:Security Best Practices* Uphold the Principle of Least Privilege: Make sure users only have the permissions they need for their tasks. This lowers the chance of unauthorized access.* Implement Strong Data Classification and Labeling Policies: Sort data by sensitivity. This helps apply the right security measures.* Regular Training and Awareness Campaigns: Teach your team about security threats and best practices. Awareness can greatly lower risks.* Ongoing Auditing and Monitoring: Check user activities and access logs often. This helps you find and fix potential security issues quickly.* Governance and Policy Enforcement: Set clear rules for app use and data access. Enforce these rules to keep a secure environment.A survey of 600 companies showed that 71.4% of Microsoft 365 business users have at least one compromised account each month. This shows how common security problems are in Microsoft 365 environments.OAuth and PermissionsOAuth 2.0 is very important for improving security in Microsoft 365 Development. This standard lets one app authorize another without sharing sensitive information like passwords. Using OAuth makes identity authentication easier, which lowers the risk of credential theft.Here are some key benefits of using OAuth 2.0:* It gives better control over access permissions. Only authorized users can access specific resources.* Connecting OAuth 2.0 with Microsoft Entra gives enterprise-scale identity features. This helps you add strong security measures to your apps.But, you also need to know about common permission-related problems in Microsoft 365 apps. Here’s a table that shows these problems, their risks, and solutions:By following these best practices and being careful about permissions, you can greatly improve the security of your Microsoft 365 applications.Microsoft 365 Development for ScalabilityScalability is very important in Microsoft 365 Development. As your organization gets bigger, your apps need to handle more work without slowing down. Planning for scalability helps your solutions change with new needs. Here are some important patterns and strategies to think about when making scalable solutions on Microsoft 365.Scalable ArchitectureWhen creating scalable architecture, pay attention to several key areas:By focusing on these areas, you can build a strong base for your apps that can grow with your organization.Performance ConsiderationsTo make sure your apps work well under heavy loads, think about these strategies:* Set a limit on the number of scale units to control costs.* Improve scale unit startup time by pre-setting nodes and allowing time for changes.* Use sharding and partitioning to manage data stores well.* Watch scaling operations to analyze and adjust the autoscaling strategy.* Choose technologies that support automatic scaling and have built-in scaling features.Also, regularly check your hardware specifications. Recommendations include using SSDs, at least 8 GB of RAM, and CPUs with four physical cores. These specs help performance under heavy loads. Before making big changes, test how network or hardware updates affect performance to avoid hurting user experience. The Microsoft Office Performance Assessment tool can help measure these effects.For custom solutions, think about these performance improvement techniques:* Efficient Database Management: Regularly clean and archive old data to improve system speed.* Minimize Customization Overhead: Balance needed customizations with system efficiency.* Leverage Caching Mechanisms: Use caching strategies to speed up response times.* Regular System Monitoring: Track performance metrics to find and fix bottlenecks early.By using these strategies, you can keep your Microsoft 365 apps responsive and efficient, even as user demands grow.Implementing Tailored ApplicationsIn Microsoft 365 Development, you can customize applications for your organization’s special needs. Customization helps make apps better and improves how users feel about them. Here are some important customization options you can use:By using these options, you can create custom applications that fit your business goals and boost productivity.Development Best PracticesWhen making and using custom applications in Microsoft 365, following best practices helps with smooth setup and ongoing care. Here are some key practices to think about:* Use the Monthly Enterprise Channel: This channel gives a mix of new features and stability, which is great for most organizations.* Implement Dynamic Collections: These collections help you send updates better, so users get the right updates at the right time.* Enable Peer Cache: This feature helps with deployment in faraway places by letting devices share downloaded content.* Create Separate Collections: Make different collections for first-time deployment and regular maintenance to make management easier.* Set Client Devices to Update Automatically: This cuts down on admin work and makes sure users have the latest features and security updates.To check how well your custom applications work, think about these methods:* Use metrics from tools like Application Insights to see daily user activity.* Regularly look at apps that are not used much for possible improvements.* Do user rese

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack

SharePoint modernization, legacy SharePoint 2010/2013 workflows, InfoPath migration, Power Apps, Power Automate, AI Builder and Copilot Studio – this episode is for people searching “SharePoint 2013 workflow retirement”, “modernize SharePoint lists”, “replace InfoPath with Power Apps”, “SharePoint Power Automate migration” or “SharePoint modernization with Power Platform”. Your SharePoint isn’t outdated because you’re lazy – it’s outdated because legacy workflows are basically bosses that refuse to retire, and this conversation gives you the practical cheat codes to turn that 2013 dungeon into a modern, AI‑powered collaboration hub without starting from scratch.

We start where the pain is loudest: brittle SharePoint 2010/2013 workflows, InfoPath forms and subsites that still “kind of work” but quietly slow everything down. You’ll hear why Microsoft’s retirement of SharePoint 2013 workflows in SharePoint Online (no new 2013 workflows since April 2, 2024 and full retirement on April 2, 2026) turns this from “someday” into a deadline, how legacy helpdesk and approval flows turn into invisible tax on your teams, and why sticking to old workflows is like running a Windows XP tower in a modern office.

From there, we move into what you actually do about it. We walk step‑by‑step through how to inventory legacy workflows and InfoPath forms, identify the real boss fights, and map them into Power Automate flows and Power Apps instead of doing a risky big‑bang rebuild. You’ll learn how to treat SharePoint lists as a stable backend while Power Apps delivers a modern, mobile‑ready UX, how Power Automate replaces brittle 2013 workflows with resilient automation, and how AI Builder and Copilot Studio join the party to auto‑tag files and remove repetitive tasks without breaking data residency or governance because model training data lives in Dataverse under controlled access.

Finally, we zoom into concrete examples and quick wins. From turning a clunky SharePoint helpdesk list into a tap‑friendly app and automated flow, to using “Create an app” directly on a list to generate your first canvas app in minutes, you’ll see how to unlock fast travel in your existing environment instead of burning it down. The goal: keep your lists, libraries and history, but upgrade how people interact with them so SharePoint stops feeling stuck in 2013 and starts behaving like a modern, Power Platform‑driven, AI‑assisted workspace.

WHAT YOU WILL LEARN

• Why legacy SharePoint 2010/2013 workflows and InfoPath forms keep your environment stuck in “2013 mode”.
• What Microsoft’s retirement of SharePoint 2013 workflows in SharePoint Online really means for you.
• How to inventory and prioritize old workflows and forms for migration to Power Automate and Power Apps.
• How to treat SharePoint lists as a solid backend and layer modern UX with canvas apps.
• How Power Automate replaces brittle approvals and helpdesk flows with resilient automation.
• Where AI Builder and Copilot Studio add value with file tagging, document understanding and bots.
• How data residency and governance work when AI Builder models train on your SharePoint data via Dataverse.
• Practical first steps and low‑risk experiments to modernize without tearing everything down at once.

THE CORE INSIGHT

The core insight of this episode is that you don’t have to burn down your SharePoint to modernize it – you keep the bones (lists, libraries, data) and upgrade how you interact with them using Power Platform and AI. Once you replace fragile legacy workflows with Power Automate, wrap your key lists in Power Apps, and selectively bring in AI Builder and Copilot Studio, your “2013 dungeon” becomes a modern, governed, AI‑powered hub that actually supports how people want to work today.

WHO THIS IS FOR

• SharePoint admins and owners responsible for legacy workflows and InfoPath forms.
• Power Platform makers and platform owners driving SharePoint modernization.
• IT leaders planning for SharePoint 2013 workflow retirement in SharePoint Online.
• Business process owners stuck with clunky ticketing, approval or tracking lists.
• Microsoft 365 architects looking to align SharePoint, Power Platform and AI under one governance model.

ABOUT THE HOST

Mirko Peters is a Microsoft 365 consultant and host of M365.FM, where he explores modern work, security and productivity with Microsoft 365, Power Platform and AI. He helps organizations turn “stuck in 2013” SharePoint environments into modern, governed, app‑ and automation‑driven platforms without losing the data and structure they rely on every day.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

Identity perimeter, Microsoft Entra ID security, MFA, Conditional Access, PIM and Zero Trust – this episode is for people searching “Entra ID security best practices”, “identity as the new perimeter”, “Conditional Access policies”, “PIM Entra ID”, “legacy auth block”, “Zero Trust identity” or “how to secure Entra ID in Microsoft 365”. Instead of staring at one more high‑level Zero Trust slide, you’ll get a grounded walkthrough of what it means when your castle walls are no longer firewalls but identity checks, and why an unprotected Entra tenant is basically a wide‑open gate where attackers stroll in dressed as your own users.

We start with the shift from network perimeter to identity perimeter. Firewalls used to be your dragons at the moat; now your business lives in browsers, cloud apps and roaming laptops, and attackers don’t charge the wall, they steal or phish credentials. You’ll hear how Microsoft’s shared responsibility model pushes your security focus onto Entra ID configuration, what “identity is the new perimeter” actually means in practice, and why relying on passwords alone is the equivalent of guarding the vault with a wooden door. From there, we go deep into MFA as your reinforced gate, why password policies and forced rotations often backfire, and how multi‑factor authentication plus modern auth closes the door on credential stuffing and basic account takeover.

Then we introduce the “smart bouncer at the gate”: Conditional Access. You’ll learn how to move from simple yes/no logins to policies that evaluate user risk, sign‑in risk, device compliance, location and session context in real time. We discuss blocking legacy authentication, enforcing compliant devices, requiring stronger factors for risky sign‑ins, and using risk‑based access so a 3 a.m. login from across the globe doesn’t just sail through because it passed MFA. We also touch on session controls, sign‑in policies and how Conditional Access turns your static password gate into a context‑aware identity perimeter that actually reflects Zero Trust thinking.

Finally, we look at privileged access and day‑to‑day operations through Privileged Identity Management (PIM), least privilege and Just‑In‑Time access. Instead of handing out permanent global admin, we talk about shrinking the blast radius with JIT admin elevation, approval workflows, access reviews and strong auth requirements for privileged roles. You’ll walk away with a practical mental model and first steps: enable MFA everywhere, block legacy auth, define core Conditional Access baselines, and then bring PIM and least privilege on top—so your Entra ID castle gate stops being the easiest way in for attackers and becomes the hardest part of your environment to walk through unchallenged.

WHAT YOU WILL LEARN

• Why identity (and Entra ID) has become your real perimeter instead of firewalls.
• How passwords, reuse and phishing keep blowing holes in traditional perimeter models.
• Why MFA is the reinforced gate and how it changes the economics of credential attacks.
• How Conditional Access acts as a smart bouncer that evaluates risk, device, location and session.
• Why blocking legacy authentication and enforcing modern auth is a foundational control.
• How to use device compliance and sign‑in risk to require stronger proof or block access.
• How Privileged Identity Management, JIT access and least privilege shrink admin blast radius.
• A practical starter roadmap to harden your Entra ID tenant without boiling the ocean.

THE CORE INSIGHT

The core insight of this episode is that in the Microsoft cloud, your real castle gate is Entra ID—not your old perimeter firewall—and if that gate is weak, every other control is working with intruders already inside. By treating identity as the primary perimeter and combining MFA, Conditional Access, PIM and least privilege, you turn Entra ID from a flimsy password door into a layered, risk‑aware gate that attackers have to fight for instead of simply walking through.

WHO THIS IS FOR

• Identity and security engineers responsible for Entra ID and Microsoft 365 access.
• Security architects and blue teamers designing Zero Trust and identity perimeters.
• IT admins moving from on‑prem AD thinking to cloud‑first Entra security models.
• CISOs and security leaders who need a crisp story for “why MFA + Conditional Access + PIM”.
• Anyone who has ever wondered if their Entra ID tenant is an open castle gate.

ABOUT THE HOST

Mirko Peters is a Microsoft 365 consultant and host of M365.FM, where he explores modern work, security and productivity with a strong focus on identity, Entra ID and cloud‑connected environments. He helps teams translate Zero Trust buzzwords into concrete Entra ID configurations—MFA, Conditional Access, PIM and least privilege—that both security and infrastructure teams can actually implement.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

Microsoft Fabric, OneLake, Direct Lake, lakehouse architecture, trial capacity and workspace strategy – this episode is for people searching “What is Microsoft Fabric OneLake?”, “Direct Lake vs Import Power BI”, “Fabric capacity planning”, “enable Fabric in Power BI tenant” or “OneLake governance Purview”. We start with the part that quietly changes everything: in Microsoft Fabric, Power BI doesn’t need to drag data back and forth anymore – with OneLake and Direct Lake mode it can query straight from the lake with performance close to import, which means fewer copies, fewer fragile refresh chains and a cleaner data estate.

From there, we frame Fabric as an engine: input with Dataflows Gen2, process inside the lakehouse with pipelines, and output through semantic models and Direct Lake‑powered reports. You’ll hear why OneLake acts like “OneDrive for your data” in a non‑fluffy way, how open formats like Delta Lake and Parquet keep you out of proprietary lock‑in, and why consolidating lakes into one governed vault feels less like marketing and more like finally having a single guild bank instead of a dozen unsynced chests across your organization. We also tackle the real anxieties: single point of failure, governance, and how Purview, lineage, sensitivity labels, monitoring and private access controls (like managed private endpoints and trusted workspace configs) are wired into Fabric so observability and compliance aren’t an afterthought.

Then we move to the big scary button: switching on Fabric in your Power BI tenant. Instead of treating it like a self‑destruct, we walk through how enabling Fabric is more like unlocking a new wing: your existing reports and datasets keep running, but you gain new objects—lakehouses, pipelines, Dataflows Gen2 and more—without auto‑migration. You’ll learn how to light up Fabric for selected users or capacities first, build a sandbox workspace, use trial capacity as your “practice arena”, and use Microsoft’s Contoso templates to stress‑test pipelines, refresh cycles and query performance before anything touches production. That way, capacity planning mistakes happen on dummy data, not payroll dashboards.

Finally, we zoom into trial capacity, workspace strategy and real‑world capacity pitfalls. We discuss why Fabric isn’t dangerous because of the toggle but because of mis‑sized workloads, what happens when you pile heavy ingestion into a tiny SKU, and how to avoid user‑visible slowdowns by isolating experiments, right‑sizing capacities and spreading high‑cost workloads intentionally. You’ll come away with a pragmatic path: turn Fabric on safely, feed OneLake with Dataflows Gen2 and pipelines, and design a workspace and capacity layout that lets your environment evolve from fragmented lakes into one governed, observable data vault that Power BI, Synapse and Data Factory can all consume directly.

WHAT YOU WILL LEARN

• How OneLake turns scattered data silos into one governed “vault” for Fabric workloads.
• Why Direct Lake lets Power BI query the lake with import‑like performance and fewer copies.
• How Dataflows Gen2, lakehouses, pipelines and semantic models form the Fabric “engine”.
• How Purview, lineage, sensitivity labels and monitoring give OneLake built‑in governance.
• What the Fabric tenant toggle actually does (and doesn’t do) to your existing Power BI content.
• How to use trial capacity, sandbox workspaces and Contoso templates to test safely.
• Common capacity and workspace mistakes that make Fabric feel slow—and how to avoid them.
• A practical rollout strategy that adds Fabric as an expansion pack instead of a risky rebuild.

THE CORE INSIGHT

The core insight of this episode is that Microsoft Fabric is not about throwing away your existing BI setup—it’s about giving Power BI, Synapse and Data Factory a shared, governed engine in OneLake so data stops living in scattered, fragile copies. Once you understand how Direct Lake, lakehouses, trial capacity and Purview‑backed governance fit together, turning on Fabric becomes less of a doomsday switch and more of an upgrade that quietly makes your data estate simpler, more observable and easier to scale.

WHO THIS IS FOR

• Power BI admins and architects considering when and how to enable Fabric.
• Data engineers and lakehouse owners designing on OneLake, Delta Lake and Parquet.
• Analytics leaders sick of duplicate lakes, extracts and broken refresh chains.
• IT and platform teams planning Fabric capacity, workspaces and trial environments.
• Anyone trying to explain “Fabric + OneLake + Direct Lake” to non‑technical stakeholders.

ABOUT THE HOST

Mirko Peters is a Microsoft 365 consultant and host of M365.FM, where he explores modern work, data and productivity with Microsoft 365, Power BI and Fabric. He helps organizations move from scattered BI projects and shadow IT lakes to governed, Fabric‑ready data estates that balance performance, compliance and real‑world usability.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

In today’s online world, security problems with identity are a significant risk for companies. By 2026, businesses with strong Unified Identity Security plans will have 50% fewer breaches than those without. Sadly, more than half of all breaches include customer personal information, such as important data like emails and tax ID numbers. As you navigate the challenges of identity security, it is crucial to understand how solutions like Conditional Access and Defender for Identity work together. This collaboration not only enhances your security but also addresses the urgent issues of managing identities effectively.Key Takeaways* Combining Conditional Access and Defender for Identity makes security better. It uses different ways to check user access. This lowers the chance of unauthorized access.* Conditional Access lets organizations create specific rules for access. These rules depend on user roles, device safety, and location. This helps control sensitive data better.* Defender for Identity keeps watch and finds threats all the time. It helps organizations act fast against suspicious actions and possible breaches.* Updating security rules often and doing practice attacks can make defenses stronger. This also helps meet industry standards.* A combined identity security plan makes management easier across platforms. It builds trust with customers and protects against new threats.Conditional Access OverviewConditional Access is an important tool in identity security. It uses different signals to make smart access decisions. This system works on a simple if-then rule. Access to resources depends on certain actions done by the user. By checking more than just passwords, Conditional Access boosts security. It makes sure the right people get access at the right times.Key FeaturesThe table below shows the main features that set Conditional Access apart from other access management tools:Benefits of Conditional AccessUsing Conditional Access gives many benefits for organizations:* Enhanced Security: By checking access with multiple factors, you greatly lower the chance of unauthorized access.* Granular Control: You can set access rules based on user roles, location, and device type, reducing unauthorized data exposure.* Improved User Experience: Smart security measures improve user experience by cutting down on unnecessary prompts, letting real users access resources easily.* Transition to a True Zero Trust Posture: This method checks every access request based on identity and device trust, lowering the attack surface.* Fewer Infosec Headaches: Organizations see lower control costs and less need for on-premises solutions, making IT easier.By using Conditional Access, you can manage access better and boost your organization’s overall security.Defender for Identity InsightsMicrosoft Defender for Identity is a cloud security tool. It helps watch over and protect identities in organizations. It works well with Microsoft Defender XDR. It uses signals from both on-site Active Directory and cloud identities. This helps you find, spot, and check advanced threats easily. Defender for Identity keeps an eye on domain controller traffic. This helps you notice strange activities during cyber-attacks.Core CapabilitiesDefender for Identity has many important features that improve your security:* 24/7 Monitoring: It watches identity sources all the time. This helps you find threats as they happen.* Behavioral Analytics: The tool looks at user behavior. It finds odd logins or rule changes that might mean a threat.* Incident Response: You can quickly act on incidents. For example, you can deactivate hacked user accounts to reduce risks.* Visibility into Authentication Traffic: Defender for Identity shows you authentication traffic and security settings. This helps you see possible weaknesses.* Detection of Identity-Based Attacks: It is made to find attacks like stealing credentials and gaining extra privileges.Advantages of Defender for IdentityUsing Microsoft Defender for Identity has many benefits over older security tools:* Proactive Threat Detection: By looking at user behavior, you can find suspicious actions before they get worse.* Integrated Security Strategy: Defender for Identity works well with other security tools. This creates a united way to protect identities.* Comprehensive Visibility: It uses different sources of threat information and behavior analysis. This gives you a clear view of your security situation.* Regulatory Compliance: The tool improves security to protect sensitive data. It also helps meet rules like HIPAA and ITAR.* Reduced Administrative Burden: Automating regular tasks makes compliance easier for your IT teams.By using the features of Defender for Identity, you can greatly improve your organization’s identity security system.Importance of Unified Identity SecurityIn today’s complicated online world, combining Conditional Access and Defender for Identity is very important for strong security. This combination helps you build a unified identity security system. It improves your overall security and lowers possible weak spots.Enhancing Security PostureUnified identity security keeps an eye on all identities in your organization all the time. This method helps you find weaknesses and makes sure you follow identity rules. By setting access rights that match business needs and laws, you greatly lower risks linked to identity management.Microsoft Defender for Identity protects your on-site identities. It uses smart technologies like machine learning and behavior analysis. This helps find and respond to threats right away. This ability improves the safety of your identity data and assets. It lets you keep track of your organization’s security status well.The combination of Conditional Access and Defender for Identity gives you many key benefits:* Visibility into Applied Risk-Based Policies: You can see the specific risk-based policies used in sign-in logs. This helps you check how well they work in your organization.* Advanced Conditional Access Features: You get better options for Conditional Access, like setting rules based on how often users sign in. This gives you more control over user access.* Unified Access Policy Management: Managing all access policies in one place makes admin tasks easier and boosts efficiency.* Enhanced Flexibility in Access Control: You can improve access control by adding different risk conditions, like location, for a stronger security system.Reducing Blind SpotsCombining Conditional Access and Defender for Identity helps fix common security blind spots that organizations have. These blind spots can cause big weaknesses if not taken care of. For example, too many privileges in service accounts and old accounts can create security problems. By automating the finding of these issues, you can manage your security better.By combining these tools, you can greatly improve your organization’s ability to find and react to security threats. AI systems can analyze thousands of frames every second. They can spot threats that human workers might miss. This ability cuts down on false alarms by telling apart normal actions from real threats, thus boosting overall security.Integration Steps for Security TeamsTo connect Conditional Access with Defender for Identity, you need to plan carefully. Follow these steps to make the integration go smoothly.Configuration Guidelines* Define Security Policies: First, set up security rules that match industry standards. This helps your organization follow best practices and meet legal requirements.* Inventory Cloud Assets: Find and list all cloud assets. This helps you know what needs protection and makes sure no accounts are left open to risks.* Apply Secure Baseline Configurations: Use secure settings on all platforms. Keeping settings the same lowers the chance of mistakes that could cause security problems.* Automate Scanning and Detection: Use tools to automatically check for mistakes in settings. This helps you find risks quickly and fix them before they get worse.* Track Configuration Drift: Watch for any changes in your settings that are not allowed. Keeping an eye on these changes helps keep your security strong and ensures you follow the rules.* Enforce Policy-Based Remediation: Set up rules that automatically fix any problems found. This helps you respond to alerts faster and makes things easier for

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack

Autonomous AI agents, digital coworkers, Copilot Studio, Teams/SharePoint/Dynamics agents, data loss prevention and oversight – this episode is for people searching “AI agents gone rogue”, “autonomous agents risks”, “digital coworkers governance”, “Copilot Studio agents safety”, “human in the loop AI agents” or “principal–agent problem in AI”. We start with the scenario you’re already walking into: Teams, SharePoint and Dynamics filling up with eager AI coworkers that observe, plan and act across your stack—often faster than humans, but without your intuition for boundaries, confidentiality or consequences.

Imagine logging into Teams to a swarm of agents promising to streamline your day. They feel like super‑powered interns, but unlike real interns they already hold entitlements and tool access, from Outlook and SharePoint to Dynamics and beyond. That’s the Microsoft + BCG model in practice: memory, entitlements and tools combining into agents that can remember past interactions, jump across systems you’ve trusted for years and execute workflows end‑to‑end. The upside is huge—threading data across silos, connecting Teams chats, SharePoint files and CRM data without endless attachments and meetings—yet the risk is just as big when these digital coworkers misinterpret goals and act with misplaced confidence.

We unpack why this isn’t just a tooling problem but a governance problem. Old‑school automation was a vending machine: you pressed a button and got the same output every time. Agents are different: they notice context, improvise steps and generate outcomes no one explicitly hard‑coded. On a natural 20, that looks like a brilliant, cross‑system report assembled in minutes. On a natural 1, it’s a confidently wrong board deck built on misaligned definitions across three systems, or a well‑meaning “cleanup” that archives the wrong financials because “you asked it to tidy project files.” The principal–agent problem shows up in your tenant: you want compliance and accuracy; the agent delivers the closest‑match interpretation of your prompt, sometimes by blasting confidential spreadsheets in an email you didn’t intend.

From there, we zoom into the new job description for managers: bosses of digital workers. You’ll hear why experts expect leadership performance to be measured partly by how many AI agents you can effectively manage, and why prompting, oversight and output verification are no longer “nice extras” but core management skills. We look at how to set escalation thresholds (when an agent must stop and ask a human), how to design prompts like system policies instead of casual chat, and how to treat verification as a non‑negotiable step when agents bridge Outlook, SharePoint, Teams and line‑of‑business apps. The result is a clear picture: your value as a leader increasingly depends on orchestrating humans and digital coworkers so they hit the same goals without creating compliance investigations in the background.

WHAT YOU WILL LEARN

• Why today’s AI agents are not macros but digital coworkers with memory, entitlements and tool access.
• How agents move across Outlook, Teams, SharePoint and Dynamics in ways that expand your attack surface.
• What the principal–agent problem looks like in real AI deployments (misaligned goals, confident mistakes).
• Why old vending‑machine automation is safer by default—and when you should still prefer it.
• How to design prompts, oversight and verification as core management skills, not afterthoughts.
• Where data loss prevention, entitlements and tool governance must tighten before agents go live.
• How human‑in‑the‑loop controls, escalation rules and output checks keep agents from going rogue.
• A practical first‑day checklist to review agent memory stores, entitlements and tools before rollout.

THE CORE INSIGHT

The core insight of this episode is that autonomous agents are not quirky side projects—they are fast, tireless coworkers that can either multiply your output or magnify your risk, depending on the guardrails you build. Once you understand how memory, entitlements and tool access turn an “agent” into a powerful but oblivious teammate, you can design prompt governance, oversight and DLP controls that keep them useful, safe and aligned with your real business goals.

WHO THIS IS FOR

• Engineering and product teams building or deploying AI agents in real workflows.
• Security, governance and risk leaders worried about data loss and over‑permissioned agents.
• People managers and team leads who will soon “manage” both humans and digital coworkers.
• Copilot Studio, Teams, SharePoint and Dynamics owners planning agent‑based experiences.
• Anyone feeling the hype around multi‑agent systems but wanting a sober risk framework.

ABOUT THE HOST

Mirko Peters is a Microsoft 365 consultant and host of M365.FM, where he explores modern work, AI and productivity with a focus on how tools behave in real organizations, not just polished demos. He helps teams turn concepts like digital coworkers, entitlements, DLP and human‑in‑the‑loop oversight into concrete guardrails that keep AI agents from going rogue across Microsoft 365 and business systems.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-copilot-ai-modern-work--6704921/support.

Managing SharePoint Site Provisioning can be hard. Many IT teams feel stressed by too many provisioning tickets. You might face problems like not having rules for many SharePoint sites. Also, doing things by hand often takes too long, which slows things down.Think about this: creating a site can take several days. This depends on when the support team is free. Last-minute requests can mess up your work and make the process harder. Employees often ask for sites without clear reasons. This leads to more problems. Fixing these issues can help your work run smoother and boost productivity.Key Takeaways* Automate SharePoint site setup to save time. This reduces manual work. It also helps create sites faster and boosts productivity.* Use the PnP PowerShell tool and templates. This keeps all SharePoint sites looking the same. It helps maintain a consistent style.* Always back up your SharePoint site templates. This protects you from losing data. Follow a backup plan and use the 3-2-1 rule for better safety.* Use good rules to manage access. This protects important information. It helps you follow the rules and makes security better.* Pick the right way to log in to SharePoint Online. Think about security needs and what you need to do for the best outcome.Prerequisites for SharePoint Site ProvisioningBefore you start automating SharePoint site provisioning, gather the right tools and permissions. This preparation helps everything go smoothly and quickly.Required ToolsTo automate your SharePoint site provisioning well, you need these tools:* PnP PowerShell Module: Install this module to use many cmdlets for SharePoint management.* PnP Provisioning Engine: Use this engine to set up your site. You can configure site columns, content types, and list definitions. You can also export your design into a template format like XML or JSON.* PowerShell Cmdlets: Use your templates on many target sites with commands like:* Connect to SharePoint Online:Connect-PnPOnline -Url “https://yourtenant.sharepoint.com/sites/targetcommunicationsite” * Invoke the site template:Invoke-PnPSiteTemplate -Path “PnP-Provisioning-File.xml” Permissions NeededYou must also have the right permissions to run provisioning scripts. The table below shows the minimum permissions needed:Having the right permissions is very important. It lets you manage site creation and setup without access problems.Importance of GovernanceGood governance is very important in your provisioning process. It sets clear rules and roles that improve security and compliance. Here are some key governance points to think about:* Access Management: Automate permission assignments based on user details.* Content Protection: Use data loss prevention policies to keep sensitive information safe.* Lifecycle Management: Automatically archive or delete sites based on set rules.By focusing on governance, you make sure your SharePoint site provisioning stays secure, compliant, and efficient.Site Template BackupBacking up your SharePoint site templates is very important. It keeps your hard work safe and helps you recover from problems. If you lose a template, making it again can take a lot of time and effort. Regular backups help you avoid confusion and keep your site provisioning consistent.Importance of BackupsYou should think about a few reasons for backing up your templates:* Data Protection: Backups protect your templates from being deleted or damaged by mistake.* Version Control: Keeping different versions lets you go back to an earlier one if needed.* Compliance: Regular backups help you follow rules and keep a record.To make sure your backup practices work well, follow these tips:* Set a good backup schedule and automate it.* Use the 3-2-1 rule: Keep three copies of data on two types of media, with one stored off-site.* Use safe off-site backups to guard against big problems.* Encrypt sensitive data for better security.* Check each backup’s quality using automated tools.* Regularly check backup rules to make sure they meet your recovery goals.Backup ScriptYou can use this PowerShell script to back up your SharePoint site templates. This script saves the template to a chosen location:# Connect to SharePoint Online Connect-PnPOnline -Url “https://yourtenant.sharepoint.com/sites/yoursite” -UseWebLogin # Define the path for the backup $backupPath = “C:\Backups\YourTemplate.xml” # Export the site template Get-PnPSiteTemplate -Out $backupPath -IncludeAllContent This script connects to your SharePoint site and saves the current site template to the backup location you chose. Make sure to change the URL and backup path to fit your needs.By having a strong backup plan, you can make sure your SharePoint site provisioning stays reliable and efficient.Connecting with PnP PowerShellConnecting to SharePoint Online with the PnP PowerShell module is very important. It helps you automate your SharePoint site provisioning. You can connect in different ways. Each way works best for different situations.Establishing ConnectionTo connect to SharePoint Online, use the Connect-PnPOnline command. This command lets you enter the URL of your SharePoint site and choose how you want to log in. Here are some common ways to connect:* Interactive AuthenticationConnect-PnPOnline -Url “https://yourtenant.sharepoint.com” -ClientId “” -Interactive* App-Only AuthenticationConnect-PnPOnline -Url “https://yourtenant.sharepoint.com” -ClientId “” -ClientSecret “”* App-Only with CertificateConnect-PnPOnline -Url “https://yourtenant.sharepoint.com” -ClientId “” -Tenant “” -CertificatePath “C:\certs\pnp.pfx” -CertificatePassword (Get-Credential)These commands help you connect safely to your SharePoint site. Pick the method that works best for your security needs and how you operate.Authentication MethodsWhen you connect with PnP PowerShell, you have different ways to log in. Each way has its own benefits and security risks. Here’s a quick look at the authentication methods:Think about the security of each method. For example, using a username and password is easy but can risk exposing your login info if not careful. On the other hand, interactive authentication allows for extra security checks, which is safer.Using OAuth2 access tokens keeps your login info safe and reduces risks. Certificate-based authentication is a secure way to handle sensitive data without putting it in scripts.By knowing these methods, you can pick the best way for your SharePoint site provisioning needs.SharePoint Site CreationMaking a new SharePoint site is easy with PnP PowerShell. You can automate this job to save time and keep things the same across your organization. Below is a script that helps you create a new site.Site Creation ScriptTo make a new SharePoint site, use the New-PnPSite command. This command lets you set different options, like the site type, title, and URL. Here are some examples of how to use this command:* New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -SiteDesignId ae2349d5-97d6-4440-94d1-6516b72449ac* Makes a new Communications Site collection called ‘Contoso’ with the given URL, using a custom design.New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -Classification “HBI”* Makes a new Communications Site called ‘Contoso’ and sets the classification to ‘HBI’.New-PnPSite -Type CommunicationSite -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso -ShareByEmailEnabled* Makes a new Communications Site that allows inviting outside users.New-PnPSite -Type TeamSite -Title ‘Team Contoso’ -Alias contoso* Makes a new Modern Team Site called ‘Team Contoso’ with the given URL.New-PnPSite -Type TeamSiteWithoutMicrosoft365Group -Title Contoso -Url https://tenant.sharepoint.com/sites/contoso* Makes a new Modern team site not linked to an M365 group called ‘Contoso’.These commands let you create different types of sites based on what you need. You can easily change them to fit your specific needs.Customizing Site SettingsYou can customize your SharePoint site when you create it to fit your organization’s needs. Here are some important customization options to think about:You can also create a Microsoft 365 Group or a Microsoft Team, which automatically includes a SharePoint site when you create the group. This makes the process easier and ensures everything is ready from the start.By using these customization options, you can create a new SharePoint site that match

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack