• Any Teams meeting will need need to be sent to the attendee(s) before the details are visible in the event body. The details will not be visible until the event has been saved and/or sent. 

• 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.

• 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.

• In order to prevent this and any possible data corruption of your calendar from occurring, we recommend that if you would like to edit a single instance of a recurring event, delete that single instance from the recurrence and create a new event where the deleted instance would have taken place. Microsoft 365 (Outlook on the web | Outlook for Windows/Mac) - Best practices when using the calendar.

• Certain attachment types are blocked in Office 365. If you are unable to view or open an attachment, please review Microsoft 365 - Unable to view/open attachment article to verify that the file type is not blocked.

• 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:

    • Microsoft 365 (Outlook on the web | Outlook for Windows/MacOS) - Work On Behalf of a Resource Calendar

  • Disable auto-accept for the resource calendar:

    • Microsoft 365 - Configure Resource Scheduling Options/Settings/Permissions

• Open the problematic email in Outlook, click More Move Actions > Other Actions > Encoding, and then change the encoding to Unicode (UTF-8).
• Or, open the email via Outlook on the web. If the CJK characters still appear, you will need to open the email in an Outlook desktop client and change the encoding.

• The reason for this is because when the message is received and processed within Office 365, the alternate address is replaced by the primary address of the account.
• A possible workaround for this is to create a matching header rule (It includes these words | in the message header...) instead - and enter the alternate address as the matching words.

• Similar behavior should be expected when the attendee accepts or declines a meeting, and when the owner of the event cancels the meeting.

After further review/discussion with Microsoft, this is working as designed. There is no workaround and Microsoft views this as part of their 'secure by default' principles.

If messages are ending up within "Junk Email" folder, please contact DoIT Help Desk so that the M365 service team can review the message.

Note: Even though Outlook clients will appear to add/save the information within the safe sender's list, when you return to this screen, the entry will not appear.

When creating a calendar event which includes a Teams meeting link via Outlook on the web or Outlook for Mac (New version), the Teams meeting link/information will not be visible within body of the event until you save the event.

Microsoft has responded that this is by design and working as expected.

• The attendees will be able to take action on the event invitation from any of the notifications, but only one response is necessary.

• This issue occurs because of Daylight Saving Time. Learn more.

There are times when you know there are events within a calendar, but your Outlook client is not showing them. What causes this delay:

• This may occur if recurring event(s) do not have an end date set. To fix this issue, set an end date for all recurring events/meetings. Learn more.
• All Outlook clients are internally coded to sync your calendars and any other calendar(s) you are subscribed to in the following priority/order:
  • Calendars within the user’s account (like Calendar and any other they have created within their account) – within minutes if not quicker
  • Group calendars – within minutes if not quicker
  • Shared mailboxes (we do not use this feature) – within minutes if not quicker
  • All other subscribed calendars (one you have read, editor, delegate permissions to) – these are synced over a 24-48 hour cycle

  The UW-Madison Microsoft 365 team has engaged with Microsoft regarding the syncing delay and Microsoft confirmed the syncing priority/order. Unfortunately, the workarounds they provided are not feasible within our environment. At this time, the only solution is to wait up to 48 hours for the data to sync.

• All clients connecting via IMAP will experience data throttling

  • Throttling causes a reduction of speed when downloading or moving a large number of messages
  • Throttling is controlled by Microsoft and cannot be removed

• 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

• Additional information on how to improve your IMAP client's performance.

Due to the issues listed above, configuring a client via IMAP is not recommended.

• Sometimes the Suggested Meeting Add-In does not schedule the event at the correct date/time, even though it did pick up the correct date/time in the email.
• The event should be deleted and recreated manually.
• Learn more about Microsoft 365 - Suggested Meetings add-in

• 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.

  • Open any Office application.
  • Go to File | Options | Trust Center.
  • Click Trust Center Settings... button.
  • Chose the Macro Settings tab.
  • Make sure to select VBA macros that are digitally signed.

  If the above steps do not work, please try the following:

  • Open Word application.
  • Go to File | Options.
  • Within 'General' page, click Privacy Settings button with "Privacy Settings" section.
  • Enable Turn on optional connected experiences check box.
  • Restart Office application.

• Add-ins not appearing in Outlook for Mac desktop client even though they are active within the Office 365 account and available within Outlook on the web.
  •  Current Work Around
    1. Start/Open Outlook client.
    2. Go to Outlook | Preferences | Privacy menu.
    3. Make sure "Turn on optional connected experiences" is selected/enabled.
    4. Close Preferences menu.
    5. Restart Outlook.

• If other users are able to use the Similarity feature, then the issue may be related to an Office application setting on the user's computer.
  • Start/Open Microsoft Word.
  • Go to Word | Preferences | Privacy menu.
  • Make sure "Turn on optional connected experiences" is selected/enabled.
  • Close Preferences menu.
  • Restart Word.
• If the above steps do not work, please try the following:
  • Start/Open Microsoft Word.
  • Go to Word | Preferences | Spelling & Grammar menu.
  • Make sure Writing Style is set to Writing and Grammar.
  • Close Preferences menu.
  • Restart Word.

• Some users may experience an issue with resource calendars not processing event invites and cancellations appropriately, even if the setting is selected to do so.
• Our current work around for this issue can be found here: Microsoft 365 - Resource Calendar Not Automatically Processing Invitations and Cancellations.

• 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..

  • Update the password on the account linked to your desktop or mobile client. You can visit the following document for more information regarding client configuration/access Microsoft 365 - Setup/configure Outlook on mobile device or desktop computer
  • Restart your mobile device or desktop client to put the change into effect.

• Role accounts migrated as service accounts will display with a period in front of the name, for example: the name 'Bucky Badger' will appear as '.Bucky Badger.' To resolve this issue, a domain admin will need to change the first and last name by following the steps provided in this document Microsoft 365 - Change your display name.

• The current work around is to not change the 'From address' until you are ready to send the email.

• Office 365 web services use browser settings to determine language. If you have multiple languages configured within a browser for translation or other purposes, Microsoft may recognize one of these additional languages and translate text automatically. Remove any additional languages besides the one which you would like to be displayed on Office 365 Web Services from your browser's settings.

• Here is the workflow for this scenario to occur:

• A UW-Madison Office 365 user is a member of the group
• The Office 365 account has auto reply (out of office) enabled
• This same account is configured in Apple Mail client
• This account has sent or replied to a message using the Apple Mail client to the Google Group 

• The above will cause an automatic reply to be sent for each additional response or reply to the Google Group conversation.

• The workaround for this is to only use Outlook clients when interacting with your Office 365 account.

• Microsoft confirmed this as a known issue/behavior. When opening another mailbox via Outlook on the web, the account control cannot be maintained to the mailbox that was opened. It will only control the account you authenticated/logged in with.

• Issue: When a meeting organizer updates a meeting by adding participants, all external attendees may receive an update if there is a corrupted image contained within the message body.
• Workaround: If a meeting organizer intends to include images in the event invite, the images should be added using the attachment feature within the message body. It is not recommended that organizers utilize the Insert pictures inline feature.

• Microsoft has made modifications to the Send Updates feature for editing meetings/events.

• Microsoft is aware of this issue/behavior and is working to resolve it.
• Workaround/solution:
  1. Either Microsoft 365 - Introducing the new Outlook for Mac or use Outlook on the web to create the calendar day event.

• For additional details on this issue, review following information.
• Workaround/solution:
  1. Start Outlook for Windows.
  2. On the "File" tab, click Account Settings in the Account Settings list.
  3. In the Account Settings dialog box, click the "E-mail" tab and then double-click your Microsoft Exchange Server account.
  4. In the 'Change Account' dialog box, click More Settings.
  5. In the 'Microsoft Exchange' dialog box, click the "Advanced" tab.
  6. Click to clear the Download shared folders check box.
  7. Click OK two times.
  8. Click Next, click Finish, and then click Close.
  9. Restart Outlook.

• In Outlook for Windows, accounts that you have full mailbox permission to -- including any linked accounts -- will be added to your account list automatically. Review the following document for further details on AutoMapping: Microsoft 365 - Automapping.
• In Outlook for Mac, accounts that you have full mailbox permissions to -- including any linked accounts -- will not be added to your account list automatically. You will need to subscribe or configure these accounts.

Important: your Netid@wisc.edu must either be licensed for Office Pro Plus or you must be running a valid licensed version of Office desktop apps. Contact your local IT staff or DoIT Help Desk to confirm the license before proceeding with troubleshooting steps below.

• Step 1: Access the keychain application and remove/delete any of the following records: Microsoft Office Identities Cache 2 | Microsoft Office Identities Settings 2 and any ADAL, Microsoft, or Office entries that are listed within the "Name" or "Kind" columns. Note: search for 'microsoft' and 'adal' within the keychain application and delete all returned results. Detailed steps.
• Step 2: Restart computer and start Outlook and see if issue persists. If issue is not resolved, continue to Step 3.
• Step 3: Completely uninstall Office for Mac - Troubleshoot Office for Mac issues by completely uninstalling before you reinstall. Important: After restarting your computer, go to next step to install Office for Mac.
• Step 4: Follow steps outlined within Office for Mac installation article.

If above steps do not resolve the problem, please see Microsoft 365 - Can't sign in to Microsoft Office, access Microsoft Outlook, or interact with Microsoft data files (Option 6).

• After installing the macOS Monterey 12.1 update, search in old versions of Outlook for Mac returns no results.
• Solution: This issue has been resolved with the release of Office for Mac version 16.57 (22011101). To apply the fix, install/update the latest Office for Mac updates. Information on how to install the latest updates can be found here: Update Office for Mac. Learn more.

• Sometimes when attempting to login to office apps, users receive this error
• To resolve this error, use Microsoft steps outlined here.
• If the previous steps do not resolve the issue, please attempt the following:
  • Within Windows, run "Settings".
  • Go to Accounts | Access work or school.
  • Remove all accounts from this area.
  • Restart Outlook and configure your account.
• If the steps outlined in the previous troubleshooting does not work, you can also try modifying a registry key. Important: Before making changes to your computer's registry, please make sure you have backed up your registry and/or working with support staff before making the changes outlined below. In addition, this process will be creating a new Outlook profile.
  • Quit out of all Microsoft applications (like Outlook, Teams, OneDrive, etc).
  • Backup Windows Registry.
  • Run "registry editor".
  • Go to 'HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity'.
  • Rename 'Identity folder to 'Identity.old'
  • Quit out of registry editor.
  • Restart computer.
  • Start Word and sign into your Office 365 account.
  • If you are using Outlook desktop client, start Outlook and configure a new Outlook profile.

• Some users may experience the inability to edit (create, edit, delete events) or assign permissions to a resource even though the user has been granted the appropriate access to the resource.
  •  Current Work Around
    1. Open Outlook
    2. Go to File > Account Settings > Account Settings
    3. Select your Exchange profile > Click "Change" > Click "More Settings" > Select the "Advanced" tab
    4. Check Use Cached Exchange Mode (if not already checked)
    5. Uncheck "Download shared folders"
    6. Click OK > Click "Next" > Click "Finish"
    7. Restart Outlook

• Workaround: The OCR feature is available in the OneNote for Windows desktop client.

• Status: The Office 365 team is working with Microsoft to find a resolution.

You may experience the below, which are a few examples of errors that can occur when trying to transfer OneNote sections. This error is temporary and is due to Microsoft experiencing high volumes of traffic to their servers.  

Workaround: These errors are temporary and should resolve themselves when the server traffic has been reduced. OneNote will continue to try to reach the server to sync the notes. OneNote for the web can be used to avoid such errors, but please read the below error notice for information on what will happen to the OneNote sections that are not synced and the web version is used. 

Below are a few possible errors that can occur when trying to sync a OneNote sections. Microsoft has notified us that the below errors occur when there is high volumes traffic to their servers. 

"We couldn't sync your notes because the server is busy. We'll try again later. (Error code: 0xE40200B4)" or "(Error Code: 0xE000145C bukxh 10007)

Workaround: The errors are temporary and should resolve themselves once traffic to the servers has lessened. Once this occurs the changes made will automatically sync.

Please note that if there are changes made to the sections on the web version of the OneNote by you or anyone with access to the OneNote, then any changes on the desktop version will be overridden. If you would like to see the changes made during the error, please go to OneNote > File > Options > Save & Backup. For more information recovering OneNote Data please see, Recovering Data from the OneNote Cache - Microsoft Support . 

• 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.

• Issue: When an owner of a team attempts to create a tag, an error message populates indicating the following: "We had trouble applying your changes. Please try again later." This error occurs due to a corruption of the users membership data.

• Workaround: User needs to be removed from the team by another owner. Once removed, they should be re-added to the team and promoted to owner. User should then be able to create tags. If there are no other owners of the team, promote a member to owner and ask them to perform the above steps.

The OPP add-on license has been removed from your UW-Madison Microsoft 365 account. If you need to continue to access Microsoft 365 desktop or mobile apps, excluding mobile Outlook and Teams apps, please consider purchasing a personal Microsoft 365 license.

Example:

On February 1st 2024, a change was made by Microsoft that capped Exchange Online 1 plans at 100GB. As such, when the OPP license was removed the change made by Microsoft took effect. For more information on this change, click here.

If you are experiencing issues, please reduce your OneDrive space or contact your Local IT Department for help to do so. Please note, this storage amount cannot be expanded, as stated by Microsoft. Note: Any OneDrive that is over its limit will be read only until the user deletes/transfers enough files to get under the new quota. No files are automatically removed.

Below are a few optional recommendations to prepare for the removal of the OPP add-on license:

1. Consult your IT department for guidance.

2. Purchase a personal Microsoft 365 license.

3. Compare feature similarities and differences between web apps, desktop apps, and mobile apps.

4. Download free Microsoft 365 mobile apps for Outlook and Teams.