Use this procedure to configure ATO SmartDocs so it can send emails from one Office 365 mailbox. Clients receive emails from this address, and sent emails appear in its Sent folder. Make sure a staff member monitors the mailbox because replies will arrive in its Inbox.
It is not compulsory to set up the Office 365 API connection for ATO SmartDocs to work because the system will send email from the centralised ddslive mailbox if the Office 365 API is not configured. However, it is highly recommended as the centralised ddslive mailbox will be retired in the future, and you will need your own mailbox for sending ATO SmartDocs documents.
Ensure you have SPF, DKIM and DMARC set up on your domain
see https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/email-authentication-about?view=o365-worldwide
see https://www.refuelcreative.com.au/blog/guide-to-google-yahoo-and-bigpond-new-email-requirements
IMPORTANT: The mailbox that you will use for sending documents needs to have a Microsoft license.
Refer to the bottom of this article for the following:
Instructions on how to set up the Office 365 API
A one‑minute video on the most common mistakes when setting up the Office 365 API.
Ensure you have adequate permissions to complete the Office 365 connection.
The page below should appear in Step 7j of the Office 365 API instructions:
If you do not see the page that asks for Grant admin consent confirmation, you likely have permissions but not admin permissions.
To fix this, go to Office 365 API > API permissions, and select the staff member who must be granted admin permissions.
The most common issue we see is that the person setting up the Office 365 API does not log out of Microsoft Azure before starting the connection in the iPracticeHub integration area.
After setup is complete, test the connection by sending an email to yourself through ATO SmartDocs:
Go to iTools > Email > Send email.
Use the new sending mailbox address in the To field.
Send a test message to confirm delivery.