The Twitter Card priority quirk

Teams prioritizes Twitter Card tags over Open Graph tags. When both are present, twitter:title overrides og:title and twitter:image overrides og:image. This is the opposite of what most platforms do and the main reason previews look different in Teams than elsewhere.

If you’ve set different values for OG and Twitter Card tags (common for per-platform optimization), Teams will use the Twitter Card values. Either make your Twitter Card tags match what you want in Teams, or remove them to let Teams fall back to OG tags.

Standard Open Graph tags

Twitter Card tags

Because of the priority quirk, these effectively control the unfurl when present:

Schema.org/JSON-LD Micro-Capabilities

Teams has a unique feature called Micro-Capabilities: richer Adaptive Card previews powered by Schema.org JSON-LD, no Teams app required. When Teams detects supported Schema.org types in your page’s JSON-LD, it renders enhanced previews with structured data.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "image": "https://example.com/image.jpg",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "datePublished": "2026-02-15"
}
</script>

This is optional and additive. Standard OG/Twitter Card tags still work for basic unfurls.

Recommended minimal setup

Keep your OG and Twitter Card tags in agreement (or only use OG tags):

<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="A brief description of the page.">
<meta property="og:image" content="https://example.com/image.jpg">
<meta property="og:site_name" content="Your Site">

If you also have Twitter Card tags, remember Teams will prefer those values.