<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Outlook on Bitsy Wiki</title>
    <link>https://wiki.bitsy.services/wiki/microsoft/outlook/</link>
    <description>Recent content in Outlook on Bitsy Wiki</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://wiki.bitsy.services/wiki/microsoft/outlook/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Outlook Mail API</title>
      <link>https://wiki.bitsy.services/wiki/microsoft/outlook/api/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/microsoft/outlook/api/</guid>
      <description>&lt;p&gt;Programmatic access to an Outlook mailbox — reading mail, sending mail, watching for new messages, managing the calendar — goes through &lt;strong&gt;Microsoft Graph&lt;/strong&gt;, a single REST API over HTTPS that fronts all of Microsoft 365. A handful of older interfaces still exist for narrow jobs, but Graph is the only one that reaches every mailbox resource and the only one still gaining features, so the rest of this section assumes it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Content-Based Auto-Reply</title>
      <link>https://wiki.bitsy.services/wiki/microsoft/outlook/content-based-auto-reply/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/microsoft/outlook/content-based-auto-reply/</guid>
      <description>&lt;p&gt;A content-based auto-reply reads each incoming email and sends back a reply whose wording depends on &lt;em&gt;what the message says&lt;/em&gt; — routing a refund request one way, a password problem another, and leaving anything unrecognized for a human. Where a vacation responder answers everything identically, this is a small event-driven program on top of &lt;a href=&#34;https://wiki.bitsy.services/wiki/microsoft/outlook/api&#34;&gt;Microsoft Graph&lt;/a&gt;: wait to be told a message arrived, fetch it, decide from its content, and reply.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
