Office 365 Email Mailboxes for New Employees
Beginning October 8, mailboxes for new faculty and staff members will be created in Office 365 Email. If your department has not yet moved to Office 365 Email, there will be some minor differences between the new hire's email and the email used by others in the department. This page summarizes some of those differences.
Important Points to Know
The new faculty or staff member will experience some temporary limitations with Outlook public folders>. They will only be able to access public folders from a Windows computer using the Microsoft Outlook desktop email client. They will not be able to modify public folder permissions. These limitations will end after the new employee's department has been moved to Office 365 Email.
Clutter and Focused Inbox
Clutter will be activated for the new employee's Inbox. It automatically moves less important messages into a new Clutter folder. Clutter can be turned off at any time. Learn more about Clutter>
In the near future, Clutter will be replaced by a new feature called Focused Inbox>
Advanced Threat Protection
Email messages that the new employee sends to or receives from other students, faculty, and staff who are also using Office 365 Email will be protected by Advanced Threat Protection. Advanced Threat Protection includes two features–Safe Links and Safe Attachments–that add another layer of security to your email. There may be a minimal delay (measured in minutes) in the delivery of email messages with attachments.
The new employee will be able to view the free/busy time of others in the department.
Shared Calendars and Mailboxes
The new employee will not be able to open a calendar or a mailbox that someone else in the department has shared with them. This limitation will end after the new employee's department has been moved to Office 365 Email.
The new employee will not be able to add entire domains to their “safe senders” list in the University’s Enterprise Spam and Virus Filter service. For example, they can add an individual such as firstname.lastname@example.org to their safe senders, but they cannot add the entire domain (e.g., @company.com) to their safe senders.