.. _client:

======================
Publishing the Add-in
======================

This chapter describes how to make the Outlook add-in available to end
users. The preferred distribution channel is centralized deployment
through the Microsoft 365 admin center; publishing to Microsoft
AppSource is covered as an alternative for public distribution.

The release bundle ships as a single ZIP (``toa-client-<version>.zip``)
that expands into three parts:

* a static ``site/`` folder (task pane + ``manifest.xml``) that gets
  published to an HTTPS origin of the operator's choosing,
* an ``apply-host`` helper script that rewrites the one per-customer
  value baked into the manifest,
* a ``README.txt`` with the short version of the procedure.

The task-pane JavaScript itself is customer-agnostic: it calls the
server via a relative ``/api/`` base path, so the only artefact that
needs per-customer customisation is ``manifest.xml``. See
:ref:`client-hosting` for the reverse-proxy setup that makes that work.

.. toctree::

   manifest.rst
   hosting.rst
   m365-deployment.rst
   appsource.rst