-
-
Notifications
You must be signed in to change notification settings - Fork 528
Notify_office365
Chris Caron edited this page Oct 6, 2024
·
16 revisions
- Source: n/a
- Icon Support: no
- Attachment Support: no
- Message Format: Text
- Message Limit: 32768 Characters per message
You will need to have a valid Microsoft Personal Account AND you will require Administrative access unfortunately (to access the Mail.Send Application Permission). More details can be found here about registering your app with Azure.
- From the Azure Portal go to Microsoft Active Directory -> App Registrations (alt link)
- Use the search bar at the top of the Azure Portal and type "Azure Active Directory." if you do not see it in front of you.
- If you still can't access anything, it's possible your organisation restricts you from doing so. You may need to reach out to them in order to proceed.
- Click new -> give any name (your choice) in Name field -> select personal Microsoft accounts only --> Register
- From here (the Overview panel) you can acquire both the Directory (
tenant) ID and the Application (`client_id') you will need. - To create your
client_secret, go to Active Directory -> Certificate & Tokens -> New client secret- The
client_secretis an auto-generated string which may have@and/or?character(s) in it. You will need to encode these characters to when pasting this into your Apprise URL. See the note section above for more details on how to do this.
- The
- Now need to set permission Active directory -> API permissions -> Add permission.
- Click on Microsoft Graph
- Click on Application Permissions and search for Mail.Send; You will want to check this box too on the match found.
- Set the Redirect URI (Web) to the following:
https://login.microsoftonline.com/common/oauth2/nativeclient- You can do this from the Authentication -> Add a platform
- Choose Web Application.
- Enter the URI
https://login.microsoftonline.com/common/oauth2/nativeclient
- Now you're good to go. 🙂
o365://{tenant_id}:{account_email}/{client_id}/{client_secret}/o365://{tenant_id}:{account_email}/{client_id}/{client_secret}/{targets}
| Variable | Required | Description |
|---|---|---|
| tenant_id | Yes | The Tenant ID Associated with your Azure Application you created. This can also be referred to as your Directory ID. |
| account_email | Yes | The Email Associated with your Azure account. |
| client_id | Yes | The Client ID Associated with your Azure Application you created. This can also be referred to as your Application ID. |
| client_secret | Yes | You will need to generate one of these; this can be done through the Azure portal (Also documented below). |
| from | No | If you want the email address ReplyTo address to be something other then your own email address, then you can specify it here. |
| to | No | This will enforce (or set the address) the email is sent To. By default the email is sent to the address identified by the account_email
|
Notes:
- If no
targetsare specified, then the notification is just sent to the address identified by{account_email} - Unfortunately the
client_secretcontains a lot of characters that can drastically conflict with standard URL rules (and thus Apprise might have difficulty detecting your client secret). The?and@characters can get generated by Microsoft and will almost definitely cause you issues.- Consider encoding this
client secretbefore putting it into your Apprise URL. Encoding the URL can be as simple as just pasting it into the form on this website. - You can also just manually escape these characters on your Apprise URL yourself manually (explained here). Simply swap all instances of:
-
?with%3F -
@with%40
-
- Consider encoding this
Send a email notification to our your Office 365 account:
# Assuming our {tenant_id} is ab-cd-ef-gh
# Assuming our {account_email} is [email protected]
# Assuming our {client_id} is zz-yy-xx-ww
# Assuming our {client_secret} is rt/djd/jjd
apprise -vv -t "Test Message Title" -b "Test Message Body" \
o365:///ab-cd-ef-gh:[email protected]/zz-yy-xx-ww/rt/djd/jjd