Legible
Scan APIChrome extension

Azure Communication Services Email

azure.microsoft.com/en-us/products/communication-services

Score 72 out of 100

An AI agent's path through Azure Communication Services Email

  1. FindCan an agent get in and find what it needs?81/100

    4 of 5 pass · 1 gap

  2. ReadCan it read what it finds?83/100

    8 of 12 pass · 4 gaps

  3. ActCan it do something with your product?Weakest step48/100

    3 of 9 pass · 6 gaps

GoalAn agent uses Azure Communication Services Email

Wider segments are worth more points. The overall adds up every check's points, so it isn't the average of the three parts. 5 checks don't count here: see why.

Easy to find, fairly easy to read, hard to use.

Azure Communication Services Email passes 4 of 5 Find checks, 8 of 12 Read checks and 3 of 9 Act checks. The weakest step is Act. One more fails there, but we'd skip it for now.

Rank
14th of 15 Email APIsOn our 9 Nov 2026 scan
Checks passed
15 of 26 counted
This scan

From our 9 Nov 2026 scan.

Board results come from one dated scan, so every company is compared on the same day. A live scan reads the site as it is now.

Details

5 checks don't count here:

  • 2 need an OpenAPI spec, and we didn't find one.
  • 1 is about sign-in our stand-in can't judge: signed or body-key.
  • 1 needs an OAuth sign-in to judge, and there isn't one.
  • 1 needs an llms.txt, and there isn't one.

Domain-level checks read azure.microsoft.com, which hosts Azure Communication Services Email.

What to fixPart 1 of 4

10 gaps to fix

Most points for the least effort. Each sits next to the file the best email API on our board shipped, as of 9 Nov 2026. One more check fails with no example to follow yet; it's below the fixes.

All 31 checks15 pass · 11 fail

Email-only

FailFind stepFix 1 of 10+7 pointsEffort: minutes, our estimate

Fix 1: Your pages don't point agents at your llms.txt

Do this: Point agents at your llms.txt from your homepage and docs page: a plain link like <a href="/llms.txt">llms.txt</a> in the footer, or <link rel="llms-txt" href="/llms.txt"> in the <head>.

llms.txt linked from your pages: a link on your pages to your llms.txt, so agents know it's there.

FailWhat we read on Azure Communication Services Email (2)

PassFrom Mailtrap, on our email API board, as of 9 Nov 2026

What the leader shippedView their file ↗

Their file
a Link header: https://mailtrap.io/llms.txt

More examples

Why it might matter

An agent mostly finds files by following links, so it may never try /llms.txt if your pages don't point to it.

Our call · Worth doing.

A link in your footer or <head>, and agents find your llms.txt without guessing its address.

Our judgement.

How we test this
  • We read your homepage and your docs page and look for a pointer to an llms.txt: a link to it, a <link> tag, a Link header with rel="llms-txt" or an X-Llms-Txt header, or a line on the page naming /llms.txt.
  • It passes when one points at an llms.txt that answers with markdown links.
  • AFDocs checks the same (llms-txt-directive).
1 more fails, with no example yet: Tools for browser agents

Nobody on the board passes our check yet

No email API on our board passes our check on these yet, so there's no example to show.

  • We didn't find tools for browser agents in your homepage's HTML or inline scripts

    Tools for browser agents: tools your web page offers to AI agents that work in a browser (a proposed standard).

    It costs a point, but it's only worth building if agents need to operate forms on your site. If they do, a browser agent may find no tools to call and have to click through instead.

    Don't do it for the score. It's still a proposed standard, and almost nobody on our boards passes our check, though Bird, Postmark and CrewAI load it from a script our check doesn't read. Build it only if agents need to operate forms on your site. Our judgement.

Show every address our checks read

Where our checks looked

Every address our checks read in our 9 Nov 2026 scan, by host. What each check read, not a recording of a visit, so there's no order.

passes on this address alone fails: select it to open the fix also read here

azure.microsoft.com

  • /robots.txt200 OKAI agents allowed, homepage reachable: also read here
  • /en-us/products/communication-services/200 OKOur scanner gets in: also read hereReadable without JavaScript: also read herellms.txt links work, and it fits: Not countedMeta description: PassEvery operation has an operationId: Not countedErrors have a schema: Not countedTools for browser agents: Fail
  • /sitemap_cs-cz.xml200 OKSitemap: Pass
  • /leaderfile-check-404404 · expected, it's a probeReal 404s: Pass
  • /llms.txt404 not found
  • /en-us/pricing/details/communication-services/200 OKReadable pricing: Pass
  • /.well-known/oauth-authorization-server404 not foundSign-in an MCP client can use: Not counted
  • /.well-known/oauth-protected-resource404 not found
  • /.well-known/openid-configuration404 not found
  • /.well-known/api-catalog404 not found
  • /.well-known/agent-card.json404 not found
  • /openapi.json404 not found
  • /openapi.yaml404 not found
  • /.well-known/agent-skills/index.json404 not found

learn.microsoft.com

  • /robots.txt200 OKAI agents allowed, homepage reachable: also read here
  • /en-us/azure/communication-services/overview200 OKOur scanner gets in: also read hereDocs page: PassReadable without JavaScript: also read hereDocs readable without a login: also read hereStructured docs page: PassDocs in Markdown: also read here
  • /en-us/azure/communication-services/quickstarts/email/send-email200 OKReadable without JavaScript: also read hereDocs readable without a login: also read hereCode samples say their language: PassDocs in Markdown: also read hereMCP server or CLI: Passnpm and PyPI packages: Pass
  • /en-us/azure/developer/azure-mcp-server/tools/azure-communication200 OKReadable without JavaScript: also read hereDocs readable without a login: also read hereDocs in Markdown: also read hereMCP server: Pass
  • /en-us/lifecycle/faq/internet-explorer-microsoft-edge200 OKReadable without JavaScript: also read hereDocs readable without a login: also read hereDocs in Markdown: also read here
  • /en-us/azure/communication-services/concepts/voice-video-calling/calling-sdk-features200 OKReadable without JavaScript: also read hereDocs readable without a login: also read hereDocs in Markdown: also read here
  • /en-us/azure/communication-services/concepts/chat/concepts200 OKReadable without JavaScript: also read hereDocs readable without a login: also read hereDocs in Markdown: also read here
  • /en-us/azure/communication-services/concepts/sms/concepts200 OKReadable without JavaScript: also read hereDocs readable without a login: also read hereDocs in Markdown: also read here
  • /llms.txt404 not found
  • /openapi.json404 not found
  • /openapi.yaml404 not found
  • /en-us/rest/api/communication/authenticationno answerAuth an agent can follow (proxy): Not counted

10 checks in red are your fixes. Select one to open it.Auth an agent can follow (proxy), Every operation has an operationId, Errors have a schema, Sign-in an MCP client can use and llms.txt links work, and it fits weren't counted.

Want a hand fixing this?

Leave your email and we'll reply about the gaps on azure.microsoft.com. One reply, no newsletter.

We store your email, this domain and its gaps, to reply. Nothing else. To be removed, email rahulu626@gmail.com

How it comparesPart 2 of 4

How Azure Communication Services Email compares

Score after each fix

Mailtrap, the leader, at 99
  1. Nowscore 72rank 14
  2. +1 fixscore 77rank 14
  3. +2 fixesscore 81rank 14
  4. +3 fixesscore 84rank 12past SMTP2GO and MailerSend

One fix at a time, in the order above. Full scores and ranks on our 9 Nov 2026 board: our maths, not a forecast.

10 gaps with a real example to follow.

Find, Read and Act against the other 14 email APIs

Out of 100. On each bar, the light mark is their median and the dark one their best.

  1. FindFind: 81, median 100, best 100.
  2. ReadRead: 83, median 95, best 100.
  3. ActAct: 48, median 83, best 96.

Where Azure Communication Services Email stands

On our board

The 15 email APIs on our board average 88, and the top score is 99.

Neighbours on the board

  1. SMTP2GO83+11
  2. MailerSend82+10
  3. Azure Communication Services Email72
  4. Amazon SES70−2

SMTP2GO 11 and MailerSend 10 ahead. Three fixes, 84, puts Azure Communication Services Email past both.

Email APIs, our 9 Nov 2026 board. Our maths, not a forecast.

What Azure Communication Services Email does well

One more thing: only 11 of the 15 email APIs on our board pass npm and PyPI packages. Azure Communication Services Email does.

The checks Azure Communication Services Email passes that are rarest among the 15 email APIs on our board.

  • npm and PyPI packagesAR-ACT-06 · 11 of 15 on our board pass this
  • Readable without JavaScriptAR-READ-01 · 12 of 15 on our board pass this
  • MCP server or CLIAR-ACT-10 · 12 of 15 on our board pass this

Compare Azure Communication Services Email with rivals

Every checkPart 3 of 4

What these checks can't tell you

  • Whether an agent can sign up and get a key. One registry found 30 of 100 developer tools blocked it.
  • Whether coding agents write current code for your API. In our small test, a 96 and a 71 came out the same: what we found.
  • Whether your bot protection lets an agent in when a person sends one. Check your CDN settings.
  • Whether ChatGPT recommends you. That depends on far more than these files.
  • What another scanner would give you. They ask different questions and weigh them differently: why the numbers differ.

All 31 checks

15 pass, 11 fail, 0 couldn't check, 5 not counted. The count on each row is how many of the 15 email APIs on our board pass that check.

Find · 4 of 5 pass · 29 of 36 points

  • PassAI agents allowed, homepage reachableAR-FIND-01checked /en-us/products/communication-services/; none of the user or search agents is blocked; checked /en-us/azure/communication-services/overview; none of the user or search agents is blocked10 of 10 points · 15 of 15 pass

    10 of 10 points · Gate, worth 10

    What our check kept, up to 60 lines or 6 KB

    User-agent: * 

# Search & filtering 
Disallow: /search*q= 
Disallow: /*/search*q= 
Disallow: /*noItems= 

# Application / internal endpoints 
Allow: /api/v2/calculator/config/ 
Disallow: /api/ 

# Tracking / query parameters 
Disallow: /*?*ep_* 
Disallow: /*?*p=* 
Disallow: /*?*cid=msft_learn_nav_* 

# WordPress 
Allow: /*wp-admin/admin-ajax.php 
Allow: /*wp-content/uploads/ 
Disallow: /*wp-admin/post.php 
Disallow: /*blog/feed/ 
Disallow: /*wp-login.php 
Disallow: /*xmlrpc.php 
# Patterns / embeds 
Disallow: /*/patterns/ 
Disallow: /*/embed/   

# China search engines 
User-agent: Bytespider 
User-agent: Baiduspider 
User-agent: PetalBot 
User-agent: YisouSpider 
User-agent: Sogou 
User-agent: HaoSouSpider 
User-agent: 360Spider 

# Overrides for parameters inside /zh-cn/ 
Disallow: /zh-cn/*?*p=* 

# Wildcard overrides that match anywhere (including inside /zh-cn/) 
Disallow: /*/search*q= 
Disallow: /*noItems= 
Disallow: /*?*ep_* 
Disallow: /*/patterns/ 
Disallow: /*/embed/ 

# Allowed paths 
Allow: /zh-cn/ 
Allow: /zh-tw/ 
Disallow: / 

Sitemap: https://azure.microsoft.com/sitemap_cs-cz.xml 
Sitemap: https://azure.microsoft.com/sitemap_da-dk.xml
Sitemap: https://azure.microsoft.com/sitemap_de-de.xml
Sitemap: https://azure.microsoft.com/sitemap_en-au.xml
Sitemap: https://azure.microsoft.com/sitemap_en-ca.xml
Sitemap: https://azure.microsoft.com/sitemap_en-gb.xml 
Sitemap: https://azure.microsoft.com/sitemap_en-in.xml
Sitemap: https://azure.microsoft.com/sitemap_en-us.xml
Sitemap: https://azure.microsoft.com/sitemap_es-es.xml

    How we test this:

    • We read robots.txt and check it doesn't disallow / for the agents that fetch for a user or find sites for AI search: ChatGPT-User, OAI-SearchBot, Claude-User, Claude-SearchBot, Perplexity-User, PerplexityBot (no robots.txt counts as allowed).
    • We show blocks on GPTBot (OpenAI model training), not scored; ClaudeBot (Anthropic model training), not scored; Google-Extended (Gemini training and grounding), not scored in v1; CCBot (Common Crawl's open dataset), not scored: blocking them is the site's own call.
    • Whether Google-Extended should be scored is a rubric v2 question, and we'll announce it before changing anything.
    • Then we fetch your homepage as LeaderfileBot and check it returns 2xx after redirects, with no challenge page.
  • PassOur scanner gets inLG-FIND-01homepage: a real answer (200); docs page: a real answer (200)10 of 10 points

    10 of 10 points · Gate, worth 10

    How we test this:

    • We fetch your homepage and your docs page as LeaderfileBot, our own scanner, and check neither answers with a challenge page, or a 401 or 403 that a normal browser gets past.
    • One blocked page is a fail; both caps your score at 39.
    • Firewalls often let in crawlers they can verify, so ChatGPT or Claude may still get in where our scanner can't.
  • PassDocs pageAR-FIND-02docs page, linked from https://learn.microsoft.com/en-us/azure/7 of 7 points · 15 of 15 pass

    7 of 7 points · High, worth 7

    How we test this:

    • We look for your docs page: the first homepage link to a docs., dev. or developer(s). subdomain of your domain, or to a /docs or /developer(s) path; with none, we try https://docs.<host>/ then https://<host>/docs.
    • It passes if that page returns 200.
    • Board companies use a docs URL we confirmed by hand.
  • Failllms.txt linked from your pagesLG-FIND-02Your pages don't point agents at your llms.txt0 of 7 points

    Your pages don't point agents at your llms.txt. An agent mostly finds files by following links, so it may never try /llms.txt if your pages don't point to it.

    0 of 7 points · High, worth 7

    How we test this:

    • We read your homepage and your docs page and look for a pointer to an llms.txt: a link to it, a <link> tag, a Link header with rel="llms-txt" or an X-Llms-Txt header, or a line on the page naming /llms.txt.
    • It passes when one points at an llms.txt that answers with markdown links.
    • AFDocs checks the same (llms-txt-directive).
  • PassSitemapAR-FIND-03sitemap listed in robots.txt, <urlset> root2 of 2 points · 15 of 15 pass

    2 of 2 points · Low, worth 2

    What our check kept, up to 60 lines or 6 KB

    <?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>https://azure.microsoft.com/cs-cz</loc>
    <lastmod>2026-08-19T22:28:26+00:00</lastmod>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://azure.microsoft.com/en-us" />
    <xhtml:link rel="alternate" hreflang="cs-cz" href="https://azure.microsoft.com/cs-cz" />
    <xhtml:link rel="alternate" hreflang="da-dk" href="https://azure.microsoft.com/da-dk" />
    <xhtml:link rel="alternate" hreflang="de-de" href="https://azure.microsoft.com/de-de" />
    <xhtml:link rel="alternate" hreflang="en-au" href="https://azure.microsoft.com/en-au" />
    <xhtml:link rel="alternate" hreflang="en-ca" href="https://azure.microsoft.com/en-ca" />
    <xhtml:link rel="alternate" hreflang="en-gb" href="https://azure.microsoft.com/en-gb" />
    <xhtml:link rel="alternate" hreflang="en-in" href="https://azure.microsoft.com/en-in" />
    <xhtml:link rel="alternate" hreflang="en-us" href="https://azure.microsoft.com/en-us" />
    <xhtml:link rel="alternate" hreflang="es-es" href="https://azure.microsoft.com/es-es" />
    <xhtml:link rel="alternate" hreflang="es-mx" href="https://azure.microsoft.com/es-mx" />
    <xhtml:link rel="alternate" hreflang="fr-ca" href="https://azure.microsoft.com/fr-ca" />
    <xhtml:link rel="alternate" hreflang="fr-fr" href="https://azure.microsoft.com/fr-fr" />
    <xhtml:link rel="alternate" hreflang="hu-hu" href="https://azure.microsoft.com/hu-hu" />
    <xhtml:link rel="alternate" hreflang="id-id" href="https://azure.microsoft.com/id-id" />
    <xhtml:link rel="alternate" hreflang="it-it" href="https://azure.microsoft.com/it-it" />
    <xhtml:link rel="alternate" hreflang="ja-jp" href="https://azure.microsoft.com/ja-jp" />
    <xhtml:link rel="alternate" hreflang="ko-kr" href="https://azure.microsoft.com/ko-kr" />
    <xhtml:link rel="alternate" hreflang="nb-no" href="https://azure.microsoft.com/nb-no" />
    <xhtml:link rel="alternate" hreflang="nl-nl" href="https://azure.microsoft.com/nl-nl" />
    <xhtml:link rel="alternate" hreflang="pl-pl" href="https://azure.microsoft.com/pl-pl" />
    <xhtml:link rel="alternate" hreflang="pt-br" href="https://azure.microsoft.com/pt-br" />
    <xhtml:link rel="alternate" hreflang="pt-pt" href="https://azure.microsoft.com/pt-pt" />
    <xhtml:link rel="alternate" hreflang="ru-ru" href="https://azure.microsoft.com/ru-ru" />
    <xhtml:link rel="alternate" hreflang="sv-se" href="https://azure.microsoft.com/sv-se" />
    <xhtml:link rel="alternate" hreflang="tr-tr" href="https://azure.microsoft.com/tr-tr" />
    <xhtml:link rel="alternate" hreflang="zh-cn" href="https://azure.microsoft.com/zh-cn" />
    <xhtml:link rel="alternate" hreflang="zh-tw" href="https://azure.microsoft.com/zh-tw" />
  </url>
  <url>
    <loc>https://azure.microsoft.com/cs-cz/contact</loc>
    <lastmod>2026-08-19T22:28:26+00:00</lastmod>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://azure.microsoft.com/en-us/contact" />
    <xhtml:link rel="alternate" hreflang="cs-cz" href="https://azure.microsoft.com/cs-cz/contact" />
    <xhtml:link rel="alternate" hreflang="da-dk" href="https://azure.microsoft.com/da-dk/contact" />
    <xhtml:link rel="alternate" hreflang="de-de" href="https://azure.microsoft.com/de-de/contact" />
    <xhtml:link rel="alternate" hreflang="en-au" href="https://azure.microsoft.com/en-au/contact" />
    <xhtml:link rel="alternate" hreflang="en-ca" href="https://azure.microsoft.com/en-ca/contact" />
    <xhtml:link rel="alternate" hreflang="en-gb" href="https://azure.microsoft.com/en-gb/contact" />
    <xhtml:link rel="alternate" hreflang="en-in" href="https://azure.microsoft.com/en-in/contact" />
    <xhtml:link rel="alternate" hreflang="en-us" href="https://azure.microsoft.com/en-us/contact" />
    <xhtml:link rel="alternate" hreflang="es-es" href="https://azure.microsoft.com/es-es/contact" />
    <xhtml:link rel="alternate" hreflang="es-mx" href="https://azure.microsoft.com/es-mx/contact" />
    <xhtml:link rel="alternate" hreflang="fr-ca" href="https://azure.microsoft.com/fr-ca/contact" />
    <xhtml:link rel="alternate" hreflang="fr-fr" href="https://azure.microsoft.com/fr-fr/contact" />
    <xhtml:link rel="alternate" hreflang="hu-hu" href="https://azure.microsoft.com/hu-hu/contact" />
    <xhtml:link rel="alternate" hreflang="id-id" href="https://azure.microsoft.com/id-id/contact" />
    <xhtml:link rel="alternate" hreflang="it-it" href="https://azure.microsoft.com/it-it/contact" />
    <xhtml:link rel="alternate" hreflang="ja-jp" href="https://azure.microsoft.com/ja-jp/contact" />
    <xhtml:link rel="alternate" hreflang="ko-kr" href="https://azure.microsoft.com/ko-kr/contact" />
    <xhtml:link rel="alternate" hreflang="nb-no" href="https://azure.microsoft.com/nb-no/contact" />
    <xhtml:link rel="alternate" hreflang="nl-nl" href="https://azure.microsoft.com/nl-nl/contact" />
    <xhtml:link rel="alternate" hreflang="pl-pl" href="https://azure.microsoft.com/pl-pl/contact" />
    <xhtml:link rel="alternate" hreflang="pt-br" href="https://azure.microsoft.com/pt-br/contact" />

    How we test this:

    • We fetch the Sitemap: URL from robots.txt, else /sitemap.xml, and check it returns 200 with a <urlset> or <sitemapindex> root element.

Read · 8 of 12 pass · 56.5 of 68 points

  • PassReadable without JavaScriptAR-READ-01homepage: 1619 words in the raw HTML; docs page: 1396 words in the raw HTML; docs surface: 8270 words in the raw HTML; docs surface: 739 words in the raw HTML; linked from the docs page: 974 words in the raw HTML; linked from the docs page: 2200 words in the raw HTML; linked from the docs page: 1840 words in the raw HTML; linked from the docs page: 1217 words in the raw HTML10 of 10 points · 12 of 15 pass

    10 of 10 points · Gate, worth 10

    How we test this:

    • We count the visible words in the raw HTML (no JavaScript run) of your homepage and your docs page, and check each has at least 150.
    • With no docs page found (AR-FIND-02), the homepage is judged alone.
  • PassDocs readable without a loginLG-READ-01docs page: readable without a login; docs surface: readable without a login; linked from the docs page: readable without a login10 of 10 points

    10 of 10 points · Gate, worth 10

    How we test this:

    • We read your docs page and up to 7 more docs pages (the ones we read for other checks, then links on your docs page).
    • A page fails when it answers 401 or 403 to a normal browser too, redirects to a sign-in page, or is a sign-in form with little else on it.
    • A redirect counts as a sign-in when it adds one: a sign-in path the page didn't have, a login subdomain, or an identity provider's site such as Okta's when the page was on another site.
    • A sign-up page, one whose title or main heading says sign up or create an account, isn't a login.
    • A refusal only to automated readers is our scanner being blocked, not a login.
    • A login on your docs page caps your score at 39; across the pages, a share of 25% or less caps it at 39, 50% or less at 59.
  • PassReal 404sAR-READ-02returned 404 for a page that doesn't exist10 of 10 points · 15 of 15 pass

    10 of 10 points · Must, worth 10

    How we test this:

    • We fetch /leaderfile-check-404, a page that shouldn't exist, and check it returns 404 or 410 after redirects.
    • Off the board, if that address refuses automated readers, we try /leaderfile-check-404.html.
  • Failllms.txtAR-READ-07No llms.txt to point agents at your docs0 of 7 points · 14 of 15 pass

    No llms.txt to point agents at your docs. An agent may have to crawl your site to find the pages that matter, instead of reading one short index.

    0 of 7 points · High, worth 7

    How we test this:

    • We read llms.txt at your site root and, if your docs live on another host, at your docs root, and check one returns 200, isn't HTML and has at least one markdown link.
    • Off the board, we also try your docs. host and /docs/llms.txt.
    • We read the first 2 MB: a larger file is judged on that part, and the result says "read the first 2 MB; the file is larger".
  • Not countedllms.txt links work, and it fitsLG-READ-02no llms.txt to read (AR-READ-07 counts that)

    Not in the score · High, worth 7

    How we test this:

    • We read the llms.txt AR-READ-07 passes on (the first with markdown links) and fetch up to 12 of its links, spread through the file, two at a time.
    • A link is broken when it answers 404 or 410, or its host doesn't exist.
    • A 2xx after redirects resolves, and so does an answer like 400, 405 or 406 that shows the address is there (an MCP endpoint answers a plain GET with 405).
    • A refusal, a 429 or a server error isn't judged.
    • The credit is the share that resolve, halved when the file runs to 50,000 characters or more, and nothing past 100,000: AFDocs' size bands.
    • With no llms.txt it isn't counted: AR-READ-07 counts that.
  • PartlyDocs pages fit an agent's contextLG-READ-04Some of your docs pages are too long for an agent to read whole6.5 of 7 points

    Some of your docs pages are too long for an agent to read whole. An agent cuts off a page past its limit, so the part it needed may never reach it.

    6.5 of 7 points · High, worth 7 · 93% credit

    How we test this:

    • On each docs page we read (up to 7) we count the characters of visible text in the raw HTML, and of its Markdown copy if it has one, and judge the page by the larger of the two: an agent reading either may be cut off.
    • Under 50,000 passes, up to 100,000 is half, more fails: AFDocs' bands, from the limits agents cut pages at.
    • The credit is the average across the pages.
  • PassMeta descriptionAR-READ-03has a meta description4 of 4 points · 15 of 15 pass

    4 of 4 points · Medium, worth 4

    What our check kept, up to 60 lines or 6 KB

    <meta name="description" content="Azure Communication Services helps you build a strong communication platform and improve experience with APIs, SMS APIs, video APIs, technology, and more."/>

    How we test this:

    • We check your homepage's raw HTML (no JavaScript run) has a non-empty meta description or og:description.
  • PassStructured docs pageAR-READ-0411 headings (h1 to h3), 1396 words in the raw HTML4 of 4 points · 13 of 15 pass

    4 of 4 points · Medium, worth 4

    What our check kept, up to 60 lines or 6 KB

    <h1>What is Azure Communication Services?</h1>
<h2>In this article</h2>
<h2>Common scenarios</h2>
<h2>Samples</h2>
<h2>Platforms and SDK libraries</h2>
<h2>Design resources</h2>
<h2>Other Microsoft Communication Services</h2>
<h2>Next steps</h2>
<h2>Feedback</h2>
<h2>Additional resources</h2>

    How we test this:

    • We check your docs page's raw HTML (no JavaScript run) has at least 2 headings (h1 to h3) with text and at least 150 visible words.
    • Off the board, a docs page that comes back as markdown counts # to ### lines outside code blocks as its headings.
  • PassCode samples say their languageAR-READ-05quickstart page: a code block with a language tag4 of 4 points · 13 of 15 pass

    4 of 4 points · Medium, worth 4

    What our check kept, up to 60 lines or 6 KB

    <code class="lang-azurecli" data-interactive="azurecli">

    How we test this:

    • On your docs surface, we look for a code block that carries a language tag: language-* or lang-* on <pre> or <code>, code-language-* on any element (a code block's wrapper, say), or a data-language or data-lang attribute.
    • In markdown files, a fenced block with a language (```ts) counts.
    • If no page shows one, we read the markdown copy each HTML page declares (a <link rel="alternate" type="text/markdown">, or its URL plus .md listed in your llms.txt), since many docs sites add the language label with JavaScript.
    • If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.
  • PassReadable pricingAR-READ-11raw text shows "free" next to a month or year4 of 4 points · 15 of 15 pass

    4 of 4 points · Medium, worth 4

    What our check kept, up to 60 lines or 6 KB

    er meeting. Number of meetings per month: 1,000 Participants in meeting using Azure Communication Services: 1 Participants in meeting using Teams: 1 (free) Average duration of meetings: 45 minutes Total Voice and Video Calling Monthly cost: See this example in the pricing calculator Example 2: Order Con

    How we test this:

    • We fetch the first homepage link with 'pricing' in its path, else /pricing (board companies: a pricing URL we confirmed by hand), and check it returns 200 and its raw text (no JavaScript run) shows a price or 'free' within 80 characters of month, mo, year or yr.
    • Off the board, a pricing address that answers with JSON counts when it has a price field.
  • PassDocs in MarkdownLG-READ-03docs page: answers Accept: text/markdown; docs surface: answers Accept: text/markdown; linked from the docs page: answers Accept: text/markdown4 of 4 points

    4 of 4 points · Medium, worth 4

    What our check kept, up to 60 lines or 6 KB

    ---
layout: Conceptual
title: What is Azure Communication Services? | Microsoft Learn
canonicalUrl: https://learn.microsoft.com/en-us/azure/communication-services/overview
breadcrumb_path: /azure/bread/toc.json
feedback_help_link_url: https://learn.microsoft.com/answers/tags/128/azure-communication-services/
feedback_help_link_type: get-help-at-qna
feedback_product_url: https://feedback.azure.com/d365community/forum/81ff6d2b-0c25-ec11-b6e6-000d3a4f0858
feedback_system: Standard
permissioned-type: public
recommendations: true
recommendation_types:
- Training
- Certification
uhfHeaderId: azure
ms.suite: office
adobe-target: true
learn_banner_products:
- azure
description: Learn how Azure Communication Services helps you develop rich user experiences with real-time communications.
author: sundiraman
manager: chpalm
services: azure-communication-services
ms.author: sundraman
ms.date: 2021-06-30T00:00:00.0000000Z
ms.topic: overview
ms.service: azure-communication-services
locale: en-us
document_id: d5c2b60c-dd58-86ec-9186-2e18720f66c5
document_version_independent_id: eda0832c-3c21-2c4d-6364-25a77556fb3c
updated_at: 2026-09-23T17:12:00.0000000Z
original_content_git_url: https://github.com/MicrosoftDocs/azure-docs-pr/blob/live/articles/communication-services/overview.md
gitcommit: https://github.com/MicrosoftDocs/azure-docs-pr/blob/2238476f4cb17931df819f6d3caf6012ed394af1/articles/communication-services/overview.md
git_commit_id: 2238476f4cb17931df819f6d3caf6012ed394af1
site_name: Docs
depot_name: Azure.azure-documents
page_type: conceptual
toc_rel: toc.json
pdf_url_template: https://learn.microsoft.com/pdfstore/en-us/Azure.azure-documents/{branchName}{pdfName}
word_count: 1181
asset_id: communication-services/overview
moniker_range_name: 
monikers: []
item_type: Content
source_path: articles/communication-services/overview.md
cmProducts:
- https://authoring-docs-microsoft.poolparty.biz/devrel/54fcef21-b24a-4ef4-9c4a-a525c23ee9a3
spProducts:
- https://authoring-docs-microsoft.poolparty.biz/devrel/8ab60220-e56b-41ff-a8bf-45b8d7ab716f
platformId: 6e8649bb-b842-d2c1-ae50-3094b528206d
---

# What is Azure Communication Services? | Microsoft Learn

Warning

**Azure Communication Services is introducing breaking changes, and some services are being retired. Learn more in the [retirement and breaking changes guide](https://aka.ms/acs-retirement-and-breaking-changes-guide).**

Azure Communication Services offers multichannel communication APIs for adding voice, video, chat, text messaging/SMS, email, and more to all your applications.

    How we test this:

    • On each docs page we read (up to 7), one Markdown answer with content passes the page: it answers Accept: text/markdown with text/markdown, declares a copy with <link rel="alternate" type="text/markdown"> that returns Markdown, or the address the page lands on, after redirects, ending in .md does (for one ending in a slash, both /page.md and /page/index.md).
    • An empty answer doesn't count.
    • The credit is the share of pages that pass.
    • AFDocs, Cloudflare's isitagentready and is-agentic check it.
  • FailStructured dataAR-READ-08Your homepage has no structured data for agents to parse0 of 2 points · 13 of 15 pass

    Your homepage has no structured data for agents to parse. An agent may have to work out basic facts about your company and product from free text.

    0 of 2 points · Low, worth 2

    How we test this:

    • We check your homepage's raw HTML has an application/ld+json block that parses as JSON and has @type or @context.
  • FailMachine-readable discovery fileAR-READ-06No .well-known file tells agents how your API or sign-in works0 of 2 points · 8 of 15 pass

    No .well-known file tells agents how your API or sign-in works. An agent may have to guess how sign-in or your API works instead of reading it from a standard file.

    0 of 2 points · Low, worth 2

    How we test this:

    • We fetch five standard .well-known files and check at least one returns 200 with valid JSON: oauth-authorization-server (RFC 8414), oauth-protected-resource (RFC 9728), openid-configuration, api-catalog (RFC 9727) and agent-card.json (A2A).
    • This list is ours: AgentReady v2.0 doesn't name one.
    • Off the board, on a miss, we also read oauth-protected-resource on the mcp., api. and docs. hosts of your domain, where that metadata usually lives, and it counts only with its resource field.

Act · 3 of 9 pass · 21 of 44 points

  • PassMCP server or CLIAR-ACT-10quickstart page: CLI command "az communication email send"10 of 10 points · 12 of 15 pass

    10 of 10 points · Must, worth 10

    What our check kept, up to 60 lines or 6 KB

    onment variable with your IDE open, you may need to close and reopen the editor, IDE, or shell in order to access the variable. Send an email message az communication email send --connection-string "yourConnectionString" --sender "<donotreply@xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.azurecomm.net>" --to "<emailalias@emaildomain.c

    How we test this:

    • Passes when AR-ACT-03 passes (your docs surface names your own MCP server, not just a mention or a blog post about one; on the board, only an MCP server with a tool that acts on the product: send, manage or query, not only search docs, since AgentReady calls this "the interface an agent acts through"), or when your docs surface shows a CLI install: brew install, npm i -g, npm install -g, pipx install, uv tool install, go install, az extension add, or curl ... | sh (or | bash).
    • A mention of MCP that isn't your own server, with no CLI install, isn't counted.
    • For board companies, the CLI half counts only a command of the product's own CLI that we confirmed by hand, like az communication email send or twilio email:send, on the pages we read or on the docs page that shows it: an install alone could be any tool (an MCP setup guide installing pnpm, say).
    • For a product inside a larger platform, the platform's MCP server or CLI counts when its docs show it covers the product.
    • An MCP server earns both this check and AR-ACT-03, because AgentReady lists them as two items.
    • If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.
  • FailOpenAPI specAR-ACT-02No OpenAPI spec for agents to read your API from0 of 7 points · 11 of 15 pass

    No OpenAPI spec for agents to read your API from. An agent may have to guess your endpoints and parameters from prose instead of reading them from a spec.

    0 of 7 points · High, worth 7

    How we test this:

    • We look for an OpenAPI or Swagger document: for board companies, a URL we confirmed by hand; then up to 2 links on your docs surface whose URL mentions openapi or swagger, or whose link text does for a .json or .yaml file (files on other sites count when your docs link them; an address written out in your llms.txt or another text file counts as a link, and its line as the link text); then /openapi.json and /openapi.yaml on your host and your docs host.
    • Off the board, a .json or .yaml link under an llms.txt heading that names OpenAPI counts as a link to a spec, or, where that section has none, a link with no file extension, and on a miss we also try those two on the docs., developers. and api. hosts of your domain.
    • It passes if one parses as JSON or YAML with an openapi or swagger key and at least one path.
    • A spec over 10 MB counts as couldn't check.
  • Passnpm and PyPI packagesAR-ACT-06quickstart page: npm install "npm install @azure/communication-email"; quickstart page: pip install "pip install azure-communication-email"7 of 7 points · 11 of 15 pass

    7 of 7 points · High, worth 7

    What our check kept, up to 60 lines or 6 KB

    npm install @azure/communication-email
pip install azure-communication-email

    How we test this:

    • On your docs surface we look for an npm install (npm, yarn, pnpm or bun) and a pip install (pip, poetry or uv) of a named package.
    • Both must appear, on any of the pages (AgentReady: npm and PyPI).
    • Off the board, uv tool install and pipx install also count as a pip install.
    • Off the board, if one is missing we also read the markdown copy each HTML page declares (a <link rel="alternate" type="text/markdown">, or its URL plus .md listed in your llms.txt), then up to 2 pages your llms.txt names for that language.
    • AgentReady v2.0 asks for SDKs and a CLI here; this check tests the npm and PyPI half, and a CLI counts under AR-ACT-10.
    • If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.
  • Not countedAuth an agent can follow (proxy)AR-ACT-01our stand-in can't judge signed or body-key auth (requests are signed)

    Not in the score · Medium, worth 4

    How we test this:

    • A stand-in: AgentReady asks for self-serve key generation with documented scopes, or OAuth metadata, and key sign-up can't be tested in code.
    • It passes if OAuth metadata parses as JSON with the field its RFC requires (issuer for RFC 8414, resource for RFC 9728), or if your docs say "API key" or "API token" (also inside a placeholder like YOUR_API_KEY) within 200 characters of a documented auth header: an X-...-Key or X-...-Token header, a header named ...-Key or ...-Token, Authorization with Bearer, or "Bearer API key".
    • The word "token" on its own doesn't count.
    • For board companies we also read the authentication page their docs link.
    • Off the board, OAuth metadata with its resource field on your mcp., api. or docs. host also counts.
    • A board company whose API signs each request (like AWS Signature Version 4) or takes the key in the request body isn't counted: this stand-in can't judge that kind of auth either way.
    • If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.
  • Not countedEvery operation has an operationIdLG-ACT-01no OpenAPI spec to read

    Not in the score · Medium, worth 4

    How we test this:

    • In the OpenAPI spec AR-ACT-02 finds, we count the operations with a non-empty operationId.
    • The credit is the share that have one.
    • With no spec, it isn't counted: AR-ACT-02 already counts that.
  • PassMCP serverAR-ACT-03MCP page: mentions an MCP server; it doesn't name the tools4 of 4 points · 14 of 15 pass

    4 of 4 points · Medium, worth 4

    What our check kept, up to 60 lines or 6 KB

    Azure Communication Services Tools - Azure MCP Server | Microsoft Learn Skip to main content Skip to Ask Learn chat experience This browser is no longer supported. Upgrade to Microsoft Edge to take advan

    How we test this:

    • On your docs surface we look for your own MCP server and quote the line: your name next to "MCP" ("Acme MCP server"), "our" or "official" MCP server, or an mcp.<your domain> address.
    • Any other mention of "MCP server" or "Model Context Protocol", like a directory or an explainer, isn't counted: it can't fail you and it earns no points, because we can't tell the server is yours.
    • A mention in a link to a blog post, or on an llms.txt line that links to one, doesn't count at all: a post about building a server isn't one you ship.
    • For board companies we read the MCP page their docs link and list the tools it documents: a server that only searches your docs counts here, as AgentReady describes an MCP server as a "standard tool protocol for docs search and actions".
    • We don't probe /mcp or call any server.
    • Off the board, OAuth metadata with its resource field on your mcp. host also counts: it's the server's own file.
    • If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.
  • Not countedErrors have a schemaLG-ACT-02no OpenAPI spec to read

    Not in the score · Medium, worth 4

    How we test this:

    • In the OpenAPI spec AR-ACT-02 finds, we count the operations that declare a 4xx, 5xx or default response with a schema, directly or through a $ref.
    • The credit is the share that do.
    • We note when they use application/problem+json (RFC 9457), the standard shape.
    • With no spec, it isn't counted.
    • The IETF's draft agent-friendly API profile, is-agentic and Alpic check it.
  • FailTools for browser agentsAR-ACT-07We didn't find tools for browser agents in your homepage's HTML or inline scripts0 of 2 points · 0 of 15 pass

    We didn't find tools for browser agents in your homepage's HTML or inline scripts. It costs a point, but it's only worth building if agents need to operate forms on your site. If they do, a browser agent may find no tools to call and have to click through instead.

    0 of 2 points · Low, worth 2

    How we test this:

    • We check your homepage's raw HTML, inline scripts included, contains modelContext (AgentReady names document.modelContext).
    • External scripts aren't fetched.
  • FailAn agent skill is publishedLG-ACT-03Agents have no skill to follow for your product0 of 2 points

    Agents have no skill to follow for your product. Without step-by-step skills, an agent may work out each task from reference pages, more slowly and with more mistakes.

    0 of 2 points · Low, worth 2

    How we test this:

    • Any of three passes: /.well-known/agent-skills/index.json on your site or your docs (or one a Link header names) lists a skill whose file answers; your docs or llms.txt link a SKILL.md that answers with a name and a description; or your docs show a skills install command, on a page we read or on up to 3 pages your docs or llms.txt link about skills or your CLI.
    • An install is npx skills add, claude plugin install, a git clone into a skills folder, or your own command line running plugin install or skills add right after the word skill.
    • An index under a folder, like /developer/, may list its files from that folder.
    • Cloudflare's isitagentready, agenticplug and Alpic check it.
  • Not countedSign-in an MCP client can useLG-ACT-04no OAuth sign-in found to judge

    Not in the score · Low, worth 2

    How we test this:

    • We look for OAuth authorization server metadata (RFC 8414): at /.well-known/oauth-authorization-server on your site, through the authorization_servers your protected-resource metadata (RFC 9728) names, and on your mcp. host.
    • It passes when it lists S256 in code_challenge_methods_supported, has scopes_supported, and has a registration_endpoint or client_id_metadata_document_supported, as the MCP authorization spec asks.
    • With no OAuth metadata, it isn't counted.
  • FailInstall shown for four languagesEM-01We didn't find an install for Go on the 3 pages we read (TypeScript/JavaScript, Python and Java found)0 of 4 points · 6 of 15 pass

    We didn't find an install for Go on the 3 pages we read (TypeScript/JavaScript, Python and Java found). An agent working in one of these languages may not find how to install your library in it.

    0 of 4 points · Medium, worth 4

    How we test this:

    • On your docs surface we look for an install in each of four languages: TypeScript/JavaScript (npm, yarn, pnpm or bun), Python (pip, poetry or uv), Go (go get) and Java (a Maven <artifactId> or a Gradle implementation line).
    • All four must appear.
    • This shows how to install, not that a package is official.
    • If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.
    • Ours, not AgentReady's.
  • FailSend operation in the specEM-02We didn't find an OpenAPI spec, so we couldn't look for a send operation in one0 of 4 points · 11 of 15 pass

    We didn't find an OpenAPI spec, so we couldn't look for a send operation in one. An agent may not find the endpoint that sends an email in your spec, and may guess it.

    0 of 4 points · Medium, worth 4

    How we test this:

    • In the OpenAPI spec AR-ACT-02 found, we look for a POST operation on a path containing mail, email, message or send.
    • No spec counts as a fail.
    • Ours, not AgentReady's.
  • FailFree tier in emailsEM-03Your pricing doesn't say how many emails the free tier covers0 of 4 points · 13 of 15 pass

    Your pricing doesn't say how many emails the free tier covers. An agent may not find how many emails your free tier allows, so it may not be able to say whether that's enough.

    0 of 4 points · Medium, worth 4

    How we test this:

    • On the pricing page AR-READ-11 reads, we look for "free" within 300 characters of a number followed by emails, messages or sends and a period (a month, a day, or 30 days), like "3,000 emails/month" or "4,000 sends in any rolling 30-day window", in the raw text (no JavaScript run).
    • A one-time allowance with no period doesn't count.
    • Ours, not AgentReady's.

How we check: every check, its points and the thresholds, from the same code that runs the scan.

Something wrong? Report it to rahulu626@gmail.com

Your next stepsPart 4 of 4

Your next steps

  1. Pick your fixes
  2. Hand them off
  3. Rescan once it's live
  4. Stay ahead of your category
  5. Then back to 1 when a rival passes you

  1. Pick your fixes

    Usually the founder or DevRel lead

    3 fixes take Azure Communication Services Email from 72 to 84, 12th of 15 email APIs, past SMTP2GO and MailerSend.

    Nothing copied yet from this browser.

    See what to fix first

  2. Hand them off

    To whoever ships it

    Fix with AI writes each fix for whoever ships it: your coding agent, an engineer, product or marketing. Open it in Cursor, as a GitHub issue or in Linear, or copy it. Nothing runs until you send it.

  3. Rescan once it's live

    Usually the engineer, after the deploy

    A rescan reads Azure Communication Services Email again and shows what now passes, the new score and who you passed.

    Last scan: 72 on 9 Nov, 14th of 15 email APIs.

    Weekly, for 4 weeks. A calendar file: no email from us.
    Bookmark this page: it opens on our 9 Nov 2026 scan, with a live scan one press away.

  4. Stay ahead of your category

    DevRel, the founder

    Rivals ship too. Watch Azure Communication Services Email with MailerSend and SMTP2GO, the nearest on the board: home keeps all three, and Rescan all there shows who moved.

Track it weekly, or scan from your terminal

Scan from your terminal

npx legible-cli azure-communication-services
+ Add a rival

No sign-up. Checks the files and URLs agents read. It doesn't test an agent using your product, or whether ChatGPT recommends you.

10 fixes · copy, or open in Cursor, GitHub, Linear

Share Azure Communication Services Email's result

From our 9 Nov 2026 scan.

  • LinkThis result, so whoever opens it sees the same.
  • A line to postWhat it passes, and a way to check their own.

Cards with a place, and README badges, are for the top 3 on a board. When a rescan lifts your score, you can share the jump.