Skip to content

Latest commit

 

History

History
77 lines (57 loc) · 2.67 KB

File metadata and controls

77 lines (57 loc) · 2.67 KB

Accounts

.. toctree::
   :hidden:

   accounts/register-app
   accounts/account-setup
   accounts/migrate-from-email-channel
   accounts/secondary-addresses
   accounts/managing-accounts

:doc:`accounts/register-app`

Use the Connect Microsoft 365 App dialog to register Zammad as an OAuth app on Microsoft.

(This step is required; read on to learn why.)

Registering Zammad as a Microsoft OAuth app
:doc:`accounts/account-setup`

Use the Add Account dialog to connect your account.

You're migrating existing email channels? Look below!

Adding your gmail account to Zammad
:doc:`accounts/migrate-from-email-channel`

Use the Migrate now! button within your email channels to quickly move your mailboxes to Microsoft 365. You can roll back if things hit the fan!

Migrate an existing email channel to Microsoft 365
:doc:`accounts/secondary-addresses`

Send and receive email at additional email addresses, all through the same mailbox/account.

Adding new aliases to your Microsoft account in Zammad
:doc:`accounts/managing-accounts`

Edit the configuration of existing accounts in the Accounts Panel.

Existing accounts can be edited from the Accounts panel.

Note

🤔

How do I use my Microsoft 365 account for outgoing system notifications?

On subscription/cloud-hosted instances, you can’t. Notifications will always come from “Notification Master <noreply@your.zammad.domain>”.

On self-hosted instances, we still don’t recommend it. Using a Microsoft account for automated, outgoing messages is risky: users who exceed Microsoft’s email sending limits can have their accounts suspended.

Set up a generic :doc:`email channel </channels/email/index>` instead, then use the :ref:`Email Notification <email-notification>` setting.