Microsoft 365 for Workflows
Your Dynatrace environment can integrate with Microsoft 365 with Microsoft 365 for Workflows 
in automation workflows. You can automate sending emails via Microsoft 365 based on the events and schedules defined for your workflows.
Set up Microsoft 365 integration
Install Microsoft 365 for Workflows
Allow Microsoft 365 outbound connections
Grant permissions to Workflows
Set up Microsoft Azure for integration with Dynatrace
Authorize connection to Microsoft Azure
Install Microsoft 365 for Workflows
To use Microsoft 365 actions, first install Microsoft 365 for Workflows from Dynatrace Hub.
To install Microsoft 365 for Workflows, you need the app-engine:apps:install permission.
- In Dynatrace Hub
, select Microsoft 365 for Workflows. - Select Install.
After you install Microsoft 365 for Workflows, you need to perform some initial steps to set up the connection between Microsoft 365 and your Dynatrace environment.
Allow Microsoft 365 outbound connections
- Go to Settings
> Preferences > Limit outbound connections. - Select Add item and add the
login.microsoftonline.comandgraph.microsoft.comdomain names. - Select Save changes.
This way, you can granularly control the web services to which your Dynatrace environment can connect.
Grant permissions to Workflows
Some permissions are required by Workflows to run actions on your behalf. Other permissions are required by actions that come bundled with Microsoft 365 for Workflows itself.
To fine-tune permissions granted to Workflows
- Go to Workflows
and select Settings > Authorization settings. - Select the following permissions besides the general Workflows permission.
app-settings:objects:read
For more on general Workflows user permissions, see User permissions for workflows.
Set up Microsoft Azure for integration with Dynatrace
Configure your Microsoft Azure tenant to establish a connection with your Dynatrace environment.
-
Open
portal.azure.comto access your Microsoft Azure tenant and navigate toApp registrationsto set up a new app. For the necessary setup steps, see Register a client application in Azure Active Directory in Microsoft Azure documentation. -
Grant your newly created Azure app the
Microsoft Graph/Mail/Mail.Sendpermission.For more information, see API permissions and Introduction to permissions and consent in Microsoft Azure documentation.
To be able to use the API to send emails in the background without a currently signed-in user, you need to select Application permissions. Delegated permissions aren't sufficient.
-
After registering the app, create a new client secret. For details, see Certificates & secrets in Microsoft Azure documentation.
To create a client secret, make sure that you either have admin permissions or are part of the app owners.
- Make sure you store the client secret Value (not the Secret ID) after creation for establishing the connection to your Dynatrace environment in the next section.
Limit mailbox access through an application access policyWe strongly recommend using a technical email address as the sender used by the Dynatrace Workflows action and limiting the permissions of your Microsoft Azure app registration to these specific mailboxes by setting up an application access policy. This ensures that only specified email addresses can be used in the app registration and eventually in Dynatrace Workflows. This helps to reduce risks from impersonation.
For details on how to set up a new application access policy, see Limiting application permissions to specific Exchange Online mailboxes in Microsoft Azure documentation.
If you don't set up an application access policy for your Microsoft Azure tenant and restrict the possible email senders, any email address of your tenant can be used as the sender for your emails sent via Dynatrace Workflows.
Authorize connection to Microsoft Azure
Microsoft 365 for Workflows requires a client secret from Microsoft Azure for authorization.
- Get the following credentials from your app registration in your Microsoft Azure tenant on
portal.azure.com.- Directory (tenant) ID: Available on the Overview menu.
- Application (client) ID: Available on the Overview menu.
- Client secret: Is the Value (not the Secret ID) of the client secret from the preceding Set up Microsoft Azure for integration with Dynatrace section.
- Return to Dynatrace, go to Settings > Dynatrace Apps > Microsoft 365 for Workflows.
- Select Add item and provide the following information.
- Connection name: Needs to be unique. Will be listed and selectable in the connection field in Microsoft 365 for Workflows.
- Directory (tenant) ID
- Application (client) ID
- "From" email address: See Limit mailbox access through application access policy in the Set up Microsoft Azure for integration with Dynatrace section.
- Type:
Client secret - Client Secret: This is the Value of the client secret from the Set up Microsoft Azure for integration with Dynatrace section.
Save your changes.
Additional notes
-
To add connection settings, you need the following permissions.
ALLOW settings:objects:read, settings:objects:write, settings:schemas:read WHERE settings:schemaId = "app:dynatrace.microsoft365.connector:connection"For details, see Permissions and access.
-
Be aware that connections are shared and can be used by all users with
app-settingsread permissions.
Send an email with workflows
-
Go to Workflows
and select 
to create a new workflow. -
In the side panel, select the trigger best suited to your needs.
-
On the trigger node, select
to browse available actions. -
In the side panel, search the actions for Microsoft 365 and select Send email.
-
Select a preconfigured Microsoft 365 connection.
-
Enter the email addresses for the recipients.
The number of email addresses is currently restricted to 10 per field.
-
Enter a subject.
-
Enter a message.
-
To test your workflow, select Run.
This workflows integration doesn't allow formatting of the subject or message. It's only possible to send plain text emails. It doesn't offer support for markup or HTML.
Action result
The Send email action provides the following result.
| Property | Description |
|---|---|
| A unique identifier required for reporting issues to Microsoft Support that is returned by the Microsoft API in the response header field |
| A unique identifier required for reporting issues to Microsoft Support that is returned by the Microsoft API in the response header field For sending emails, this is identical to |
Troubleshooting
The following are solutions to problems some people have.