You can contact Microsoft directly to make a case for supporting a specific feature in Office 365, by submitting your idea to Microsoft's Office 365 feedback and suggestions site at https://office365.uservoice.com/
For a list of issues that have been resolved, click here.
You may also want to review support documentation from other services that may be related to the issue you are experiencing.
The issues listed below apply to all or multiple email/calendar clients.
Individuals who receive an email that is signed with a security certificate, may not be able to respond or forward that message when using the Outlook on the web client. The UW-Madison Office 365 team is working with Microsoft for a solution.
Workaround: Use a desktop client to answer S/MIME encoded email.
Cannot print calendar in Outlook on the web's new interface as of 09/2019. Per Microsoft, this is known behavior/issue.
Workaround 1: Print calendar using the browser option instead of using the print option in Outlook on the Web.
Workaround 2: Save the calendar as a PDF using Internet Explore and then print the calendar events.
Microsoft recommends voting for the option to print calendars in Outlook on the web's new interface here: https://office365.uservoice.com/forums/264636-general/suggestions/38460925-not-printing-details-of-the-meetings-calendar.
When editing a single instance of a recurring event, the edited event may not appear appropriately for invitees of that event.
Unable to view/open attachment
If a resource calendar is set to auto-accept meeting invitations, the title/subject of the event will list the name of the organizer when the resource calendar is viewed
This only occurs only if the resource calendar is invited to the event. If the event is scheduled on behalf of the resource -- i.e., the resource calendar creates the meeting -- this will not occur.
Microsoft is aware of this issue and has stated that the feature is working as designed.
There are two ways to work around this issue:
Use the resource calendar to create the meeting. In order to do this, you will need at least read and write permissions to the resource. Select your client below for instructions:
Disable auto-accept for the resource calendar:
Desktop versions of Outlook may display some emails in CJK characters (aka. Chinese characters, Han characters, kanji, etc.)
Filtering based on which alternate address in the To field does not produce the expected results.
When calendaring between different systems (e.g.,Gmail, Yahoo!, etc. to Office 365 and vice versa), the attendee may receive anywhere between 0 and 2 invitations.
Sending an event invite to an "@groups.wisc.edu" address -- will result in all Office 365 members receiving up to 3 notifications of the event.
If a Novell/GroupWise user invites an Office 365 resource calendar to an all day event, the event may appear from 7:00pm to 7:00pm the next day.
From March 1 - March 31, if an Office 365 user receives an event invitation from an external calendar system, the event time will be one hour behind.
Calendar clients (in most case mobile clients) may not load/sync or load/sync very slowly.
Email clients that are configured via IMAP will experience a variety of limitations and performance issues.
All clients connecting via IMAP will experience data throttling
If throttling occurs when you are attempting to move mail, you may lose messages. For information on how to avoid this issue, click here.
Most IMAP flags are not supported in Office 365. Only the "Read/unread", "Important", and "Recent" flags are supported
If you have a client configured via IMAP, Outlook on the web will show drafts of messages you have already sent in message threads
For information on how to improve your IMAP client's performance, click here.
Due to the issues listed above, configuring a client via IMAP is not recommended.
Issues involving Office 365 service accounts:
Service accounts hidden from the Global Address List (GAL) by default. However, it takes a few moments for this setting to be enabled, meaning that for the first five (or so) minutes after creation, the service account will be displayed in the GAL.
When a service account is hidden from the GAL, the only way to subscribe to its calendar is to use the Add calendar option within the email invitation that is sent as a result of the service account sharing it's calendar.
A service account cannot be deleted within ten minutes of creation
Suggested Meeting Add-In places event at incorrect time and/or on incorrect date.
Unable to install the plug in for an Office application - receive the following error: "Add-in Error Your system administrator has blocked add-ins from the Office Store".
If other users are able to install this add-in, then the issue may be related to an Office application setting on the user's computer.
Problem with resource calendars not automatically processing event invitations and cancellations
Changing your NetID password
When changing your NetID password, you must ensure that you update your clients and mobile devices accordingly and restart them because Office 365 has no facility to terminate active client sessions..
Service account display names suddenly changes to include a "." in front of the name
User receives bounce-back messages from firstname.lastname@example.org
When sending as someone else in Outlook desktop client, if you save the message as a draft, it will disappear.
When using Office 365 web services, text appears in a language other than your 'default' Office 365 language
The issues listed below apply only to Outlook on the web. Issues occur in all browsers, unless otherwise specified.
Error "An internal server error occurred. The operation failed" when attempting to add/change image for a resource/shared mailbox.
Microsoft has made modifications to the Send Updates feature for editing meetings/events.
The issues listed below apply to one or more desktop version of Outlook. If a version is not specified, the issues applies to multiple versions of Outlook. Learn more about client support.
When you view items in the secondary mailbox, new items may not appear or items seem to be missing or items that you had deleted still appear in the secondary mailbox.
Outlook for Windows will automatically load any account that you have been granted full mailbox permissions to, Outlook for Mac will not.
User attempts to run Outlook for Mac (or any other Office for Mac application) and receives an error similar to the following: "Your account, [account name], doesn't allow editing on a Mac, to learn more, contact your admin about your office plan."
Search in Outlook for Mac returns no results after installing macOS Monterey 12.1
Error - Sorry! There was a problem, please try again.
Error - Sorry, another account from your organization is already signed in on this computer. (or "Something went wrong")
Unable to edit or assign permissions to or create/edit/delete events on a resource when granted editor/owner rights in Outlook for Windows.
Add-ins not appearing in Outlook for Mac desktop client
Issue: Users attempting to change their default Teams apps will initially see the change go into affect; however, their change will eventually revert back to the default settings. The issue will not appear immediately and can sometimes take approximately 15 minutes or more to appear.
Status: Microsoft plans to roll out a fix in the next couple of updates to Teams.
Issue: When a Group has a large number of external members, this can result in the sender being blocked by Microsoft if they include the "Add channel" option to the Teams invitation. Basically sending suspicious messages to external recipients is consistent with compromised account behavior, the accounts are being flagged and in some cases blocked from sending additional messages.
Workaround: If the Office 365 Group includes a large number of external members you should not include it as a channel on the meeting invite. People can invite the Group, they just shouldn't add the channel. Outlook on the web and Outlook desktop clients do not have the option to add a channel to the invitation so they don't run into this issue.
Status: Microsoft has resolved the issue.