Blog Post

Apps on Azure Blog
3 MIN READ

Announcing public preview: Markdown for Agents in Azure App Service

jordanselig's avatar
jordanselig
Icon for Microsoft rankMicrosoft
Aug 03, 2026

Today, we are announcing the public preview of Markdown for Agents in Azure App Service. This feature gives AI agents and other tools a cleaner way to consume content from an App Service app. When a client requests Markdown, App Service can automatically convert the app's HTML response to Markdown without requiring changes to the application code.

Why Markdown for Agents?

Web pages often contain scripts, styles, and HTML markup that are useful to browsers but add noise when the content is sent to an AI model. Markdown for Agents removes that extra markup and returns a smaller, text-focused response that is easier for agents to process and can reduce token usage.

In internal testing across more than 637,000 pages, converted Markdown responses were 97 percent smaller at the median than the source HTML, with a median conversion time of 2 milliseconds. Results vary based on the page and its content.

Public preview availability

Markdown for Agents is available in public preview for Windows apps on Azure App Service in all public regions. The app must use an App Service plan in the Basic tier or higher.

No additional authentication setup is required for Markdown conversion. Your app's existing authentication, authorization, and network access controls continue to apply.

This feature is only supported on Windows App Service at this time. Support for Linux apps will come later this year.

Enable Markdown for Agents

During the public preview, you can enable the feature through the REST API, ARM/Bicep template, or the Azure CLI using az rest. Dedicated Azure CLI commands and portal support are planned for a future update.

Azure CLI with az rest

Replace the placeholders with your subscription ID, resource group, and app name:

az rest --method patch --url "https://management.azure.com/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.Web/sites/<APP_NAME>?api-version=2026-03-15" --headers "Content-Type=application/json" --body '{"properties":{"aiIntegration":{"markdown":{"enabled":true}}}}'

Verify the setting:

az rest --method get --url "https://management.azure.com/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.Web/sites/<APP_NAME>?api-version=2026-03-15" --query "properties.aiIntegration.markdown"

To disable the feature, send the same PATCH request with enabled set to false.

ARM template

Add the following property to your Microsoft.Web/sites resource using API version 2026-03-15:

"properties": {
  "aiIntegration": {
    "markdown": {
      "enabled": true
    }
  }
}

Bicep

resource webApp 'Microsoft.Web/sites@2026-03-15' = {
  name: appName
  location: location
  properties: {
    serverFarmId: appServicePlanResourceId
    aiIntegration: {
      markdown: {
        enabled: true
      }
    }
  }
}

Request a Markdown response

After enabling the feature, request an HTML page from your app with the Accept: text/markdown header:

curl -i -H "Accept: text/markdown" "https://<APP_NAME>.azurewebsites.net/"

A successfully converted response includes these headers:

Content-Type: text/markdown; charset=utf-8
x-markdown-source: easy-markdown

The response body contains Markdown generated from the page's HTML. Common content such as headings, paragraphs, links, lists, images, emphasis, and code is preserved, while script and style content is removed.

Pages that cannot be safely converted may return their original HTML. Clients should check the Content-Type and x-markdown-source response headers before processing the response as Markdown.

What's next

Linux support is planned before the feature reaches general availability. We also plan to add dedicated Azure CLI commands and a portal experience in future updates.

Share your feedback

Try Markdown for Agents with your Windows App Service apps and let us know how it works for your agent scenarios. Share feedback, questions, and feature requests in the comments below.

Updated Aug 19, 2026
Version 2.0
No CommentsBe the first to comment