ÐßÐßÊÓƵ

Yes. You have either Full or Folder Access.  

• Full Access permission allows a user to open the shared mailbox from his/her account and act as the owner of that mailbox. While accessing the shared mailbox, the user can:
  • Create calendar items
  • Read, view, delete, and change email messages
  • Create tasks and calendar contacts

However, a user with Full Access permission can't send email from the shared mailbox unless they also have Send As or Send on Behalf permission.

Note:  Only an O365 administrator can assign Full Access to an individual user.

• Folder Access, account owners or others with Full Access can:
  • Share folders
  • Calendars
  • Contacts  
  • Assign permissions as necessary

Yes. You can either Send As or Send on Behalf.  

• Send As allows a user to impersonate the shared mailbox when sending mail. For example, if Sally opens the shared mailbox Marketing Department and sends an email, it will look like the Marketing Department sent the email.

Note: Only an O365 administrator can assign Send As permissions for an individual user.

• Send on Behalf allows a user send email on behalf of the shared mailbox. For example, if John logs into the shared mailbox Reception Building 32 and sends an email, it look like the mail was sent by “John on behalf of Reception Building 32”.

Note: Only an O365 administrator can assign Send On Behalf permissions for an individual user except where noted.

• Owner - Create, read, modify, and delete all items and files, and create sub-folders. As the folder owner, you can change the permission levels others have for the folder (Does not apply to delegates.)
• Reviewer - Read items and files only
• Editor - Create, read, modify, and delete all items and files

Note: With Editor permissions, a delegate has send-on-behalf-of permission. Sent messages contain both the managers and delegates names. Message recipients see the managers name in the Sent On Behalf Of box and the delegates name in the From box.

Starting October 1, 2022, Microsoft will be removing legacy authentication used by (POP3, IMAP, MAPI).

Legacy (or basic) authentication is characterized by a client or network protocol which is incapable or not configured to do modern authentication.

A client which sends both the username and password to the application. an application using the username and password to get a logon token on behalf of the user.

This is because legacy authentication is not as secure as modern authentication.

• If you are using Microsoft’s Outlook client, you are not affected. Outlook stays current and is the only mail application that is currently 100% supported by both ÐßÐßÊÓƵ and by Microsoft.
• However, if you are still using an email client such as Thunderbird, Mail on iOS 10 or older/MacOS 10.14 or older, or certain older proprietary Android mail apps - you will be impacted and need to use Outlook.

Download and use Microsoft Outlook for free for your phone or computer for access to ÐßÐßÊÓƵ email. If your phone or computer does not support Outlook, you can continue to access ÐßÐßÊÓƵ email through your browser.

Microsoft Outlook

If you are able to download Microsoft Outlook on your device, then it is supported.

No, as Microsoft's roadmap for change indicates that they are on the path to deprecate legacy authentication.

LU Email is provided through Microsoft Office 365, subsequently these changes will affect ÐßÐßÊÓƵ University users.

Please check to ensure your device meets the compatibility requirements for LU email, and download Outlook for your device.