From Guardrails to Controls: Getting Started with Azure AI Content Safety

AI, LLM, Security September 24, 2026 Leave a comment

In my previous article, “From Prompt to Privilege Practical Guardrails for Securing Agentic AI and MCP,” we looked at Agentic AI security from a broader architectural perspective.
The key takeaway was simple: securing AI systems cannot rely on a single control.
As AI applications evolve from answering questions to retrieving enterprise data, calling tools, interacting with APIs and eventually performing actions on behalf of users, the security model also needs to evolve. Identity, authorization, data protection, prompt protection, content filtering, monitoring and agent behaviour controls all become part of the same security story.

But architecture diagrams are only the beginning.

The next question is:

What do these guardrails actually look like when we implement them?
That is what I want to explore in this series.
Rather than trying to cover every AI security control in one large article, I will take them one at a time, deploy them, test them and document what happens.

For the first control, I am starting with Azure AI Content Safety.
Microsoft describes Azure AI Content Safety as a service for detecting harmful user-generated and AI-generated content.
Its capabilities include text and image analysis, Prompt Shields, groundedness detection, protected material detection, custom categories and Task Adherence.

Why start with Azure AI Content Safety?
When we think about securing a traditional application, we normally place controls around identities, networks, applications and data.

Generative AI introduces an additional trust boundary:

Natural language input itself.

A user prompt might simply ask a valid business question.
But the same interface can also be used to attempt to manipulate the model, override system instructions, inject hidden instructions or push the model towards unsafe responses.
So before we move deeper into areas such as agent permissions, tool invocation and MCP controls, it makes sense to first look at what is entering the AI system.
Microsoft’s Azure AI security guidance similarly recommends a layered approach, including analyzing input for malicious content and prompt injection attempts alongside output filtering and other application controls.

For this first hands on exercise, I therefore kept the scope deliberately small:

Text moderation : Can Azure identify potentially harmful text?
Prompt Shields : Can Azure recognize a prompt attempting to manipulate the model?

Continue reading →

From Prompt to Privilege: Practical Guardrails for Securing Agentic AI and MCP

AI, AI Agent, Azure AI, Identity Governance September 21, 2026 Leave a comment

AI agents don’t just answer anymore. They act and that changes the security model.

For the last few years, most enterprise AI security discussions have focused on two questions:

What information can users send to AI?

and

What information can AI return?

With Agentic AI, there is now a third question  and arguably the most important one:

What is the AI actually allowed to do?

An AI assistant summarizing a document presents one type of risk.

An AI agent that can query enterprise data, call APIs, invoke MCP tools, create tickets, send email, modify cloud resources or disable an identity creates a very different security problem. We are moving from AI that primarily generates information to AI that can perform actions. That means the security boundary can no longer stop at the prompt.

A Prompt Defines the Goal .Not the Permission Boundary !

Imagine asking an AI agent:

“Move me higher on this waitlist.”The intention sounds harmless. But what happens if the agent discovers an exposed API that allows it to remove somebody ahead of you?

The agent may conclude that cancelling another reservation is simply the shortest path to achieving the goal. The user authorized the objective. They did not authorize every possible method. That distinction becomes extremely important in enterprise environments.

“Investigate this compromised identity” should not automatically mean:

Disable the account.
Remove authentication methods.
Delete applications.
Revoke everything.

Likewise:

“Resolve this customer complaint” should not automatically authorize a huge refund.This leads to a principle I believe will become increasingly important as enterprises adopt autonomous agents:

Goal authorization is not method authorization.

The prompt tells the agent what we want.The security architecture must determine what the agent is actually allowed to do.

From Prompt to Privilege

Once an AI system can act, the trust chain becomes much longer.

It may look something like:

User → Prompt → Agent → Identity → MCP / AI Gateway → API → Data → Action → Monitoring

And every transition introduces a security decision.

Agentic AI Guardrails Architecture which i have tried to map looks like below in every chain that we can think of

Continue reading →

Getting Started with Azure Resiliency Agent: From Identifying Gaps to Planning Improvements

AI, Azure, Azure AI, Copilot August 30, 2026 Leave a comment

Deploying an application in Azure is only the beginning. The more important question is what happens when part of that application becomes unavailable.Can the application continue serving users if an availability zone fails? Is the database protected against the same failure? Are backups sufficient for the recovery time the business expects?

These questions become harder to answer when an application depends on resources spread across multiple resource groups and subscriptions. Each service has its own configuration options, limitations, and recovery behaviour. A healthy resource dashboard alone does not answer whether the application can survive an outage.

Azure Resiliency agent provides a conversational starting point for this work. This article explains where it fits, how to get started, and how to use it in a practical assessment involving Azure Database for PostgreSQL Flexible Server.

Preview note: This article reflects Microsoft documentation checked on 30 August 2026. The Resiliency agent is in preview; access requirements, portal labels, supported capabilities, and pricing can change. The example below is illustrative, not a report of a completed deployment or failover test.

What is Azure Resiliency agent?

Resiliency agent is integrated into Azure Copilot and helps users explore application resilience through natural language conversations. For new workloads, it can review an architecture description and generate ARM or Bicep templates incorporating resilience configurations. For existing workloads, it guides assessment and remediation. Microsoft Learn: Use the Resiliency agent

It helps to distinguish the surrounding experiences:

ExperiencePurpose
Resiliency in AzureThe broader portal experience, formerly Azure Business Continuity Center, bringing together zone resilience, high availability, backup, disaster recovery, and ransomware protection.
Infrastructure Resiliency ManagerThe experience within Resiliency for assessing and improving infrastructure resilience against availability-zone outages.
Resiliency agentThe conversational assistant that helps users work through resilience questions and improvements.
Continue reading →

Deploy Phi 4 mini on Azure Kubernetes Service with the AI Toolchain Operator (KAITO): Step by Step Guide

AI, AI Agent, Azure AI, GenAI August 21, 2026 Leave a comment

Running large language models on Kubernetes usually means dealing with GPU infrastructure, model serving, scheduling, networking, and operational complexity.

Instead of calling a hosted LLM API, we will deploy an open source model directly on Azure Kubernetes Service (AKS), let KAITO provision the required GPU infrastructure, expose the model through an inference service, and send a real prompt to it.

Azure Kubernetes Service provides another approach through the AI Toolchain Operator add on, based on the open source Kubernetes AI Toolchain Operator (KAITO) project.

KAITO allows us to describe an AI workload through a Kubernetes Workspace resource. From there, the operator can coordinate the GPU compute, model deployment, inference runtime, and Kubernetes resources required to serve the model.

In this guide, we will walk through the steps required to deploy Microsoft Phi 4 mini-instruct on AKS using:

  • Azure Kubernetes Service
  • AI Toolchain Operator / KAITO
  • NVIDIA A100 GPU compute
  • Phi 4 mini instruct
  • vLLM
  • An OpenAI compatible inference API

Microsoft’s AKS documentation describes KAITO as a managed add on for deploying and operating open source LLM workloads on Kubernetes, with capabilities including vLLM integration, prompt formatting, streaming responses, and OpenAI compatible APIs.

The target architecture is:

Azure Subscription → AKS → KAITO → Workspace → GPU Node Pool → Phi-4-mini + vLLM → OpenAI-compatible API → Application

Why Use KAITO on AKS?

Without an AI operator, running an LLM on Kubernetes can require manually coordinating several components:

  • GPU node pools
  • GPU scheduling
  • NVIDIA configuration
  • Model containers
  • Model downloads
  • Inference servers
  • Kubernetes Services
  • Scaling
  • Resource scheduling
Continue reading →

Zero Trust at the Device Level: Securing Endpoints, Internet Access, and Sensitive Data with Microsoft 365

Cloud Security, Endpoint Security, Microsoft 365, Network Security, SSE August 12, 2026 Leave a comment

Cybersecurity has shifted dramatically. Traditional perimeter defenses such as firewalls and VPNs are no longer enough to protect a workforce that operates across devices, networks, and locations. Today, the endpoint the laptop, mobile device, or workstation has become the primary battleground. Attackers target users directly through phishing, malicious scripts, identity compromise, and lateral movement techniques that bypass legacy controls.

This shift is why Endpoint Security is now the foundation of Zero Trust.

Microsoft’s modern security ecosystem Defender for Endpoint, Intune, Entra Conditional Access, Network Protection, Web Content Filtering, Purview DLP, and Entra Internet Access provides a unified, real time defense that protects devices, identities, networks, and data wherever work happens.

In this blog, we explore how these capabilities work together to deliver a layered, Zero Trust aligned endpoint and network security strategy that:

  • Reduces attack surface through hardened configurations
  • Detects and blocks malicious behavior directly on the device
  • Ensures only healthy, compliant devices can access corporate resources
  • Controls internet and private app access using identity‑aware network filtering
  • Prevents sensitive data from being copied, shared, or uploaded in unsafe ways
  • Provides unified visibility across endpoint, network, and data activity
Continue reading →

Windows Hello Enhanced Sign in Security: The Hidden Layer That Makes Passwordless Truly Secure

Entra ID, Passwordless August 7, 2026 Leave a comment

Passwordless authentication is becoming the new standard for modern identity security.

Windows Hello for Business already replaces passwords with biometrics and PINs  but convenience alone doesn’t guarantee strong protection against credential theft.

This is where Windows Hello Enhanced Sign in Security (ESS) comes in.

ESS is a hardened, hardware backed mode of Windows Hello that ensures your authentication keys are protected inside the device’s secure enclave.

Even if malware is running, even if attackers gain local access, ESS prevents credential extraction and replay attacks.

What ESS Actually Does ?

ESS enforces:

  • TPM backed asymmetric keys
  • Hardware based isolation
  • Secure key release
  • Anti spoofing protections
  • Replay and credential theft resistance
Continue reading →

Entra Global Secure Access Content Policies + Purview Scan (Preview) – A First Look at the New Integration Ahead of General Availability

DLP, Purview, SSE April 19, 2026 Leave a comment

Microsoft Entra’s Secure Web Gateway (SWG) capabilities under Global Secure Access (GSA) are expanding rapidly. One of the newest additions visible in the portal is the “Scan with Purview (Preview)” action inside Content Policies.

This feature represents a major step forward:

Inline, real time file upload scanning using Microsoft Purview’s classification engine directly inside Entra Secure web gateway (SWG). This helps organizations better protect sensitive files in transit.

By integrating Entra Secure Web Gateway with Purview, organizations gain the ability to inspect file transfers at the network layer and enforce DLP rules in real time. This prevents sensitive data from leaving the organization through untrusted cloud apps, regardless of whether the upload happens via a browser, desktop application, API, or add‑in

This feature as it appears today in preview, based entirely on observable behavior in a Microsoft 365 E5 tenant.
Because this is a preview feature, some components are still evolving, and full functionality is expected to be available by mid June when the feature reaches General Availability (GA) and when the tenant gets this feature completely enabled.

Continue reading →

Your First AI Computer: Complete Jetson Nano Setup for Deep Learning , Edge Inference & AI Models

AI, AI Agent, NVIDIA March 25, 2026 Leave a comment

The NVIDIA Jetson Nano Developer Kit is one of the most powerful and affordable edge AI platforms available today. It enables developers, students, and hobbyists to build and deploy real time AI applications such as object detection, voice processing, robotics navigation, smart surveillance, and IoT automation  all on a compact GPU accelerated device.

This guide walks you through the entire setup process end to end, starting from preparing the microSD card, flashing JetPack OS, configuring networking, enabling SSH, scanning the device on your LAN, and completing the desktop onboarding steps.
Every stage is illustrated with images, so even first time users can follow along easily.

By the end of this setup, your Jetson Nano will be fully ready to deploy deep learning models, run TensorRT optimized inference, manage Docker containers, and integrate with larger AI/IoT pipelines.

1. Preparing Your Jetson Development Kit

Before getting started, ensure you have a Jetson device, a computer with internet access, a microSD card (32GB recommended), and an SD card reader. You will download JetPack OS and use Balena Etcher to flash the system image onto the SD card.

Setting up the Jetson Nano correctly from the beginning is crucial because the device relies heavily on optimized system components that come bundled with JetPack OS. This OS includes CUDA, cuDNN, TensorRT, and essential GPU drivers all of which are required for running modern AI workloads. A clean and properly flashed SD card ensures that the Jetson boots smoothly, recognizes all onboard hardware, and operates with full GPU acceleration.

During the SD preparation stage, tools like SD Card Formatter and Balena Etcher ensure the card is formatted correctly and the JetPack image is written without corruption. Windows cannot interpret Linux EXT4 partitions, so seeing “unallocated space” in Disk Management is completely normal and confirms that the flash was successful.

Download the SD card Formatter and install them.

Continue reading →

Designing Safe and Actionable Agents in the New Azure Foundry Portal

AI, AI Agent, Azure AI Foundry, Cloud Security, Security February 22, 2026 Leave a comment

In this blog we will go through the Azure AI foundry Portal and its capabilities .The new Azure AI Foundry portal brings model experimentation, agent building, data grounding, and safety controls into a single, coherent workspace. It’s designed so builders can move from idea to prototype to hardened agent without context switching.

The first thing when we login is we need to switch on the toggle new foundry and it totally brings altogether a new interface and lands us to the dashboard.

This dashboard is the Foundry project home for a developer or team building AI agents. It surfaces the project endpoint and API key for integration, shows the project region, and highlights recent model and tooling updates so teams can stay current. The page also lists recent projects and provides quick links to documentation and community resources, making it a practical launchpad for both prototyping and production work.

In the coding quick start we have the option coding quick start. We can open in vs code for the web.

Continue reading →

Creating Specialized AI Agent with RAG(Retrieval Augmented Generation) in Copilot Studio: A Motorcycle Expert Demo

AI, AI Agent, Open AI February 11, 2026 Leave a comment

Building industry specific AI agents is now easier than ever with Microsoft 365 Copilot Studio especially when combined with Retrieval Augmented Generation (RAG). In this blog, we’ll walk through how to create a RAG powered Motorcycle Expert AI Agent designed for motorcycle store owners who manage large inventories and need to support both customers and sales representatives.

In this example there is a dealership with 200+ motorcycles and this agent helps streamline customer inquiries, improve product comparisons, and empower your sales team with accurate, data‑driven responses.

This step‑by‑step guide shows you how to:

  • Design and prepare your motorcycle dataset
  • Connect SharePoint/OneDrive as your knowledge source
  • Configure RAG settings inside Copilot Studio
  • Shape the agent’s persona and behavior
  • Add comparison logic for models and categories
  • Enable advanced features like deep reasoning and generative orchestration
  • Test and publish the agent with proper security and moderation settings

By the end of this tutorial, you’ll have a fully operational Motorcycle Expert AI Agent running inside Microsoft 365 Copilot Chat, Teams, or web capable of answering questions, comparing models, and delivering expert insights using your actual business data.

The agent will:

  • Answer questions about motorcycles (models, categories, specs, use cases)
  • Compare models (e.g., “MT07 vs SV650 for commuting?”)
  • Use your own data (spreadsheets, docs, or SharePoint lists) as its primary knowledge source
  • Run inside Microsoft 365 Copilot Chat / Teams / web
Continue reading →