[Index]
Overview
This feature allows you to manage Microsoft Exchange Online mailboxes and calendars from within VOSS Automate, including assigning access and calendar permissions to users and team members licensed for Microsoft Office.
Using automation, it is possible to model the end-state of a user's mailbox configuration during their on-boarding or offboarding workflow. For example, it is possible to have the correct retention policy or archiving status set when a user's mailbox is being on-boarded. Or automatically have email forwarding and automated replies set when the user's mailbox is being offboarded.
Note
Any admin role (Provider, Customer, Site) can access and work with Microsoft Exchange mailboxes, provided that Microsoft is enabled at the hierarchy.
Related Topics
Configure Microsoft Tenant Connection Parameters in the Core Feature Guide
Overbuild for Microsoft in the Core Feature Guide
Microsoft Exchange Integration
The diagram displays the workflow steps for integrating VOSS Automate with Microsoft Exchange:
To access the flowcharts, view the topic via the release documentation at: https://documentation.voss-solutions.com/automate.html
The table describes the steps in the Microsoft Exchange integration workflow diagram:
Integrate Microsoft Exchange | Description |
---|---|
|
When adding the new Microsoft tenant and you're using Microsoft Exchange, you must either generate a certificate or import an existing certificate and have Automate manage it. Automate pushes the certificate to the PowerShell proxy. |
|
Once the Microsoft tenant is configured, perform a sync from the tenant configuration screen. This syncs in all Microsoft entities configured on the tenant, including Microsoft Exchange components. |
|
To prepare for the overbuild that will move synced in Microsoft entities to the sites (including Microsoft Exchange components), add the Microsoft Exchange authentication credentials to the network device lists (NDLs) for sites with subscribers requiring mailbox management in VOSS Automate. |
|
Microsoft users must be included in the overbuild settings. An overbuild moves Microsoft Office 365 users to the sites, based on the model filter criteria defined in the overbuild settings. Microsoft 365 users includes users enabled for Microsoft Teams and Microsoft Exchange on the Microsoft Cloud portal. |
|
Once you've set up VOSS Automate for integration with Microsoft Exchange Online, synced in mailboxes, and run the overbuild to move users and mailboxes to the sites, you can manage these mailboxes and calendars for users and users and teams from within VOSS Automate:
|
Supported Microsoft Exchange Mailboxes in VOSS Automate
Four types of Microsoft Exchange mailboxes are supported in VOSS Automate:
User mailboxes are created for individual Microsoft Office 365 users on the Microsoft Cloud portal, while shared mailboxes, room mailboxes, and distribution groups can be created on the Microsoft Office portal or in VOSS Automate.
Any changes made to the mailboxes and their associated calendars are synced between the Microsoft Cloud portal and VOSS Automate. This allows a VOSS Automate admin user to manage mailboxes from within VOSS Automate, and have these changes seamlessly update on the Microsoft Cloud.
The table describes the Microsoft Exchange mailboxes supported in VOSS Automate, and the ways in which you can work with these mailboxes:
Mailbox type | Description |
---|---|
User | User mailboxes are assigned to a single, licensed, Microsoft Office user. These mailboxes are created on Microsoft Exchange Online and synced in to VOSS Automate. The ability to manage access permissions on user mailboxes and calendars is useful where you need to allow other users to view, send, or receive emails on behalf of the mailbox owner. For example, to grant access to an executive assistant, or to monitor the mailbox of a user who is unable to attend to their emails or calendar items while out of office. |
Shared | Shared mailboxes can be created on Microsoft Exchange and synced in to VOSS Automate, or they can be added, updated, or deleted on VOSS Automate, and any changes are then synced back to the Microsoft Cloud portal. Shared mailboxes are useful for groups of individual users or for teams. For example, a shared mailbox might be used for a support or sales team, with different members having the same or custom access and calender permissions on the shared mailbox. The owner, or user principal, of a shared mailbox is a 'dummy', unlicensed user on the Microsoft Cloud, and does not add to the VOSS Automate subscriber count. The user principal name of a shared mailbox is auto-generated based on the display name you define. |
Room | Room mailboxes can be created on Microsoft Exchange and synced in to VOSS Automate, or they can be added, updated, or deleted on VOSS Automate, and any changes are then synced back to the Microsoft Cloud portal. Rooms are entities, typically an actual room at a physical location, that become a user for the purpose of creating the Microsoft Exchange mailbox. The entity name is the user principal name of the room mailbox. |
Distribution Group | Distribution Groups can be created on Microsoft Exchange and synced to VOSS Automate, or they can be added, updated, or deleted on VOSS Automate, and any changes are then synced back to the Microsoft Cloud portal. A distribution group is typically used to send emails to a group of recipients. You can add owners (one or more), for a distribution group in VOSS Automate, as well as modify owners. |
Access permissions on Microsoft Exchange mailboxes define the ownership rights and mailbox access permissions of one or more users for the mailbox. When configuring access permissions on a mailbox, you select a user from a list of users at the same hierarchy level as the mailbox, and select their access role permissions, for example, Read and Manage, Send As or Send on Behalf.
Calendar permissions allow you to assign a combination of role access permissions, such as Owner, and individual permissions, such as Delete All Items, to one or more users, on the calendar associated with the mailbox.
You can assign or remove access permissions and calendar permissions on all mailbox types, for users that exist at the same site as the mailbox.
Manage Microsoft Exchange Mailboxes in VOSS Automate
This procedure updates Microsoft Exchange user mailboxes, and adds, modifies, and deletes Microsoft Exchange shared mailboxes, room mailboxes, and distribution groups.
Note
You can only add or delete shared mailboxes, room mailboxes, and distribution groups in VOSS Automate. User mailboxes may be updated in VOSS Automate, but they can be added or deleted only on the Microsoft Cloud portal.
Log in to the Automate Admin Portal.
Go to (default menus) Microsoft Subscriber Management > Exchange
Choose the menu for the relevant mailbox type, either User Mailboxes, Shared Mailboxes, Room Mailboxes, or Distribution Groups.
View the summary list view of the mailbox type you selected.
Note
The Located At column in the list view displays the hierarchy level of mailboxes. Some may be at the customer level, and some may have been moved to a site.
Microsoft Exchange mailboxes are initially synced in at the customer level, and must be moved to the sites, either manually (via the list view or the mailbox management screens), or when running the overbuild.
Separate menu items are available for recipient types of mailboxes: User Mailboxes and Shared Mailboxes. If required when a user if off-boarded, the User Mailboxes entry can be converted to a Shared Mailboxes entry. Refer to the additional API operations available for the subscriber's mailbox ArchiveStatus at Microsoft Subscribers.
Do you want to ...
Update mailbox settings:
For all mailbox types | You can:
On the Delegation tab you can set permissions and calendar permissions. To do this, select a mailbox user and assign access rights. |
For user mailboxes |
Configuration templates associated with the Quick Add Group allows you to set default values when adding or removing the subscriber. See the following settings in Quick Add Subscriber Groups:
Available fields:
|
For shared mailboxes |
|
For room mailboxes |
|
For a distribution group | You can:
|
Note
Delete is allowed only for shared mailboxes, room mailboxes, or distribution groups.
Assign or remove permissions:
Note
Calendar permissions are only relevant for user, shared, and room mailboxes. For distribution groups, only mailbox access permissions are relevant.
When deleting (removing) permissions, the Microsoft cloud portal may take a few minutes to process the update, which may cause a delay for the refreshed data to reflect in the Automate GUI.
Save your changes.
Related Topics
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
User mailbox | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Principal Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Display Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Email Aliases |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Retention Policy |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Archive status |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Delegation | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Permissions | Please note that any update in MS Exchange can take up to 5 minutes to be reflected. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Access Rights |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Calendar Permissions | Please note that any update in MS Exchange can take up to 5 minutes to be reflected. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Access Rights |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Email forwarding | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Forward all emails sent to this mailbox |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Forward to an internal email address |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Forward to an external email address |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Deliver message to both forwarding address and mailbox |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Automatic replies | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Automatic replies |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Reply to all senders inside the organizations from this mailboxes |
|
||||||||||||||||||||||||||||||||||||||||||||||||
External Audience |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Reply to all senders outside the organizations from this mailbox |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom attributes | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 01 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 02 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 03 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 04 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 05 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 06 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 07 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 08 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 09 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 10 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 11 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 12 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 13 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 14 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Custom Attribute 15 |
|