Office 365 Users | Send Notification rule
Rule description
This rule sends an email to the specified Microsoft 365 user scope. It can be used as a standalone rule or in a runbook or in conjunction with a Web Action.
When to use this rule
This rule takes all the users returned by the rule query section and sends them an email using the settings in the action settings.
You can use this rule in these scenarios:
To send notifications to a certain group of Microsoft 365 users.
As part of a runbook. You should set Use previous provision rule results instead of this query to Yes. In this case, the rule will take the users from the output of certain supported provisioning rules instead of directly through this query section.
As a linked rule to a web action or an automation rule. For details please see How to configure one rule to run after another rule or a web action.
Rule settings
Query section
| Setting name | Description |
|---|---|
General Settings | |
Use previous provision rule results instead of this query |
When used in a runbook, will take the users from the output of certain supported provisioning rule instead of directly through this query section. |
| Limit scope to this Azure AD Administrative Unit |
This setting defines the search query scope. To improve query performance, limit the scope to a specific Entra ID administrative unit. IMPORTANT: To test the rule configuration, limit the rule scope to an administrative unit that contains test accounts or objects. |
| Query criteria | (missing or bad snippet) |
More options | |
Properties to Display |
Each object property defined in this setting matches the column that will be displayed in the Web Portal for this web query. To display additional columns, add the required properties to the Properties to display list. To add extension attribute 1 that is synchronized from AD, you need to use a value like:
Copy
|
System properties |
(missing or bad snippet) |
Post-query filter |
To hide unwanted data based on criteria, not supported by the Microsoft 365 query criteria above, set the filtering conditions here. TIP: For optimal performance, use the Query criteria above to filter objects whenever possible. |
Sort by |
Sort result objects list. |
MS Graph query condition (OData) |
By default, Query criteria are used. But when the MS Graph query condition is specified, it overrides the Query criteria setting. See this article for examples: How to use Query Builder dialog for Query Criteria and Filter rule settings. |
Initialization script |
Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule. Due to the PowerShell limitations, it is not possible to use calculated expressions in query criteria. That is the point where the initialization script can help. You can initialize a global variable in this setting and then use it in query criteria. IMPORTANT: To use a variable, declared in the initialization script, in the query scope, it must be global: Example: Update AD users, created in the last ten days.
|
|
Limit result set
|
This setting is used to optimize performance by limiting the number of objects returned by the Microsoft Graph API. Unlike query criteria, any post-filters on the returned objects are applied after they are returned, which means that the final set of returned objects could be less than the number configured here despite these objects existing in the source system. |
MS Graph advanced queries |
Enables consistency level eventual which uses an index that might not be up-to-date with recent changes to the object. |
Exclude shared mailboxes |
Specify if shared mailboxes should be excluded. |
Action section
| Setting name | Description |
|---|---|
| User email attribute | Specify user mail attribute. |
| To | Specify if the user object's email address (selected attribute) should be used or User's manager email address. Also, you can select the custom recipient. |
| CC, Bcc | Email address where the copy will be sent. |
| From | Users can receive emails from default SMTP from address. |
| Subject |
Email subject. TIP: It is possible to customize email subjects by using different tokens, see Customizing an automation rule or web action output email. |
| Message |
Message text. TIP: It is possible to customize email messages by using different tokens, see Customizing an automation rule or web action output email. |
| Limit the number of emails sent per minute |
An integer value that represents the number of emails sent per minute by this rule. To change the default value, navigate to Configuration > Settings > Email Settings (SMTP). The default limit for Microsoft 365 SMTP gate is 30 emails per minute. |
Advanced Options | |
| Write to selected attribute | Specify the user attribute where the notification timestamp will be written. If this setting is empty no timestamp will be written. |
| Attribute value | Specify the value that will be written to the selected attribute after every notification. |
Output Section
This section defines the output format of this rule.
To get more information about this section, please see the Rule Output section article.
Enforce/Schedule Section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Rule Enforce/Schedule section article.
Comments
0 comments
Please sign in to leave a comment.