Configure Synchronisation and Delivery Using Microsoft 365 (formerly Office 365) / Azure Active Integration

Jump to:

• Azure Active Integration
• Azure Active Delivery

Microsoft 365 (formerly Office 365) / Azure Active Integration

Introduction

This integration enables recipients to sync straight from Microsoft 365 (formerly Office 365) into the Phishing Tackle platform. Once configured, recipients will automatically synchronise every 15 minutes (by default) as they are added and removed from Microsoft 365 (formerly Office 365), keeping information up to date.

Configure Application

1. Log in to the Microsoft Azure portal.
   
2. Click "Azure Active Directory"
3. Then "App registrations"
4. And "New registration"
   
   
5. Name: Enter an application name (this will be displayed to users of the app)
6. Supported account types: Select "Accounts in any organizational directory and personal Microsoft accounts", then hit "Register"
   • Note: Nothing is required in the "Redirect URI"

Get Application ID and Tenant ID

1. From the App Registrations page, within Azure Active Directory, click "All Applications" then select your newly configured application.
   
2. Copy the "Application (client) ID" & "Directory (Tenant) ID" 
   
   
   Then, from the Phishing Tackle Platform:
   
   • Go to "Organisation" > "Settings"  > "Active Integrations" and hit "ADD INTEGRATION"
     
     
     
   • Paste the Application ID and Tenant ID into the corresponding boxes (Note: You will need to enter more data in the next section, so leave this window open for now)
     

Generate Secret Key

1. Go back to your newly configured application within the Azure Active Directory and click "Certificates & secrets"
   
   
2. Click "New client secret"
   
   
3. Add a suitable Description.
4. Select 24 Months then hit Add
   • NOTES: This is the longest-dated expiration Microsoft will allow, make a note of the date so you can create a new one in 2 years!
   • If you are not happy to set it to 24 months, please ensure to set it for the length of your contract  with Phishing Tackle, otherwise the synchronisation/delivery will stop working during your service.
5. Under the Value heading, copy the newly created secret key (Note, if you navigate away from this page it will hide the key forever, so make sure to copy it now to avoid having to repeat the process)
   
   
   
   • Then paste the secret key into the Add New Integration window still open from the previous step (NOTE; if you saved the new integration before entering the key, just click the dropdown box next to it and click "Edit", then add the secret key)
   • PRO TIP:

     If you have any shared mailboxes in Microsoft 365 (formerly Office 365) they will be imported as recipients.

     To avoid importing shared mailboxes, check the "Include only Licensed Mailboxes" box.

     

     As shared mailboxes do not require an Office 365 license, this is an effective method to filter out any non-user mailboxes.

   • Hit SAVE
     

Add Permissions

1. Go back to your newly configured application within the Azure Active Directory and click "API permissions", (NOTE: You will notice there is already a "User.Read" permission created under Microsoft Graph, ignore this and do not delete it)
   
2. Click "Add a permission"
3. Hit "Microsoft Graph"
4. Select "Application permissions"
   
   
   
5. Expand "Directory" and click the checkbox next to "Directory.Read.All"
   
   Then do the same for the following permissions:
   Group > "Group.Read.All"
   User > "User.Read.All"
   
   To enable Microsoft Azure Active Delivery, add the following permission:
   Mail > ReadWrite
   
   Then press "Add permissions"
   
   
6. Check all permissions match as per the image below
   
7. Then hit "Grant admin consent for [your organisation]"
   • NOTE: The image shows "Phishing Tackle" but this will be the name of Your Organisation.

With the above steps completed, the recipients will synchronise between Microsoft 365 (formerly Office 365) and the Phishing Tackle platform. 

For tips and best practices when using Active integration, see here

What is Microsoft Azure Active Delivery? 

The Microsoft Azure Active Delivery method allows you to bypass all external mail routing and inject emails directly to the mailboxes of your recipients. This negates the need for any additional allowlisting.

To enable the use of this delivery method, simply add the Application Permission:  Mail > "ReadWrite"  to the API permissions in Step 5 of the guide above.

Once the above steps are in place, you will be able to deliver mail by selecting Microsoft Azure Active Delivery during STEP 2 - RECIPIENT INFORMATION of the phishing campaign creation wizard.

PRO TIP:

You can set the default sending method to always use Azure Active Delivery within the Organisation Settings (Organisation > Settings > Email Campaigns)

Should you require any further assistance, please contact our support team by clicking here.