Resume Assistant is available in Word for Office 365 on Macs and Windows computers, and in Word for the web when you are signed in to your personal Microsoft account (not your work or school account). Only a few locale and language settings are supported. From your Windows PC, access the Microsoft Remote Desktop assistant to configure it for remote access from another device using the Remote Desktop apps for Windows, macOS, iOS or Android. To start the download, click the Download button. The application will start and you can run the application by clicking.
-->The Microsoft Online Services Sign-In Assistant provides end user sign-in capabilities to Microsoft Online Services, such as Office 365. The MOS SIA installs client components that allow common applications, such as Microsoft Outlook and Lync, to authenticate to Microsoft Online Services.
This article applies to both Office 365 Enterprise and Microsoft 365 Enterprise.
Read this article to learn how Office 2013 and Office 2016 client apps use modern authentication features based on the authentication configuration on the Office 365 tenant for Exchange Online, SharePoint Online, and Skype for Business Online.
Note
Legacy client apps, such as Office 2010 and Office for Mac 2011, do not support modern authentication and can only be used with basic authentication.
Availability of modern authentication for Office 365 services
For the Office 365 services, the default state of modern authentication is:
Turned on for Exchange Online by default. See Enable or disable modern authentication in Exchange Online to turn it off or on.
Turned on for SharePoint Online by default.
Turned on for Skype for Business Online by default. See Enable Skype for Business Online for modern authentication to turn it off or on.
Note
For tenants created before August 1, 2017, modern authentication is turned off by default for Exchange Online and Skype for Business Online.
Sign-in behavior of Office client apps
Office 2013 client apps support legacy authentication by default. Legacy means that they support either Microsoft Online Sign-in Assistant or basic authentication. In order for these clients to use modern authentication features, the Windows client has have registry keys set. For instructions, see Enable Modern Authentication for Office 2013 on Windows devices.
Read How to use Modern Authentication (ADAL) with Skype for Business to learn about how it works with Skype for Business.
Office 2016 clients support modern authentication by default, and no action is needed for the client to use these new flows. However, explicit action is needed to use legacy authentication.
Click the links below to see how Office 2013 and Office 2016 client authentication works with the Office 365 services depending on whether or not modern authentication is turned on.
Exchange Online
The following table describes the authentication behavior for Office 2013 or Office 2016 client apps when they connect to Exchange Online with or without modern authentication.
| Office client app version | Registry key present? | Modern authentication on? | Authentication behavior with modern authentication turned on for the tenant (default) | Authentication behavior with modern authentication turned off for the tenant |
|---|---|---|---|---|
| Office 2016 | No, AlwaysUseMSOAuthForAutoDiscover = 1 | Yes | Forces modern authentication on Outlook 2010, 2013 or 2016 More info | Forces modern authentication within the Outlook client. |
| Office 2016 | No, or EnableADAL = 1 | Yes | Modern authentication is attempted first. If the server refuses a modern authentication connection, then basic authentication is used. Server refuses modern authentication when the tenant is not enabled. | Modern authentication is attempted first. If the server refuses a modern authentication connection, then basic authentication is used. Server refuses modern authentication when the tenant is not enabled. |
| Office 2016 | Yes, EnableADAL = 1 | Yes | Modern authentication is attempted first. If the server refuses a modern authentication connection, then basic authentication is used. Server refuses modern authentication when the tenant is not enabled. | Modern authentication is attempted first. If the server refuses a modern authentication connection, then basic authentication is used. Server refuses modern authentication when the tenant is not enabled. |
| Office 2016 | Yes, EnableADAL=0 | No | Basic authentication | Basic authentication |
| Office 2013 | No | No | Basic authentication | Basic authentication |
| Office 2013 | Yes, EnableADAL = 1 | Yes | Modern authentication is attempted first. If the server refuses a modern authentication connection, then basic authentication is used. Server refuses modern authentication when the tenant is not enabled. | Modern authentication is attempted first. If the server refuses a modern authentication connection, then basic authentication is used. Server refuses modern authentication when the tenant is not enabled. |
SharePoint Online
The following table describes the authentication behavior for Office 2013 or Office 2016 client apps when they connect to SharePoint Online with or without modern authentication.
| Office client app version | Registry key present? | Modern authentication on? | Authentication behavior with modern authentication turned on for the tenant (default) | Authentication behavior with modern authentication turned off for the tenant |
|---|---|---|---|---|
| Office 2016 | No, or EnableADAL = 1 | Yes | Modern authentication only. | Failure to connect. |
| Office 2016 | Yes, EnableADAL = 1 | Yes | Modern authentication only. | Failure to connect. |
| Office 2016 | Yes, EnableADAL = 0 | No | Microsoft Online Sign-in Assistant only. | Microsoft Online Sign-in Assistant only. |
| Office 2013 | No | No | Microsoft Online Sign-in Assistant only. | Microsoft Online Sign-in Assistant only. |
| Office 2013 | Yes, EnableADAL = 1 | Yes | Modern authentication only. | Failure to connect. |
Skype for Business Online
The following table describes the authentication behavior for Office 2013 or Office 2016 client apps when they connect to Skype for Business Online with or without modern authentication.
| Office client app version | Registry key present? | Modern authentication on? | Authentication behavior with modern authentication turned on for the tenant | Authentication behavior with modern authentication turned off for the tenant (default) |
|---|---|---|---|---|
| Office 2016 | No, or EnableADAL = 1 | Yes | Modern authentication is attempted first. If the server refuses a modern authentication connection, then Microsoft Online Sign-in Assistant is used. Server refuses modern authentication when Skype for Business Online tenants are not enabled. | Modern authentication is attempted first. If the server refuses a modern authentication connection, then Microsoft Online Sign-in Assistant is used. Server refuses modern authentication when Skype for Business Online tenants are not enabled. |
| Office 2016 | Yes, EnableADAL = 1 | Yes | Modern authentication is attempted first. If the server refuses a modern authentication connection, then Microsoft Online Sign-in Assistant is used. Server refuses modern authentication when Skype for Business Online tenants are not enabled. | Modern authentication is attempted first. If the server refuses a modern authentication connection, then Microsoft Online Sign-in Assistant is used. Server refuses modern authentication when Skype for Business Online tenants are not enabled. |
| Office 2016 | Yes, EnableADAL = 0 | No | Microsoft Online Sign-in Assistant only. | Microsoft Online Sign-in Assistant only. |
| Office 2013 | No | No | Microsoft Online Sign-in Assistant only. | Microsoft Online Sign-in Assistant only. |
| Office 2013 | Yes, EnableADAL = 1 | Yes | Modern authentication is attempted first. If the server refuses a modern authentication connection, then Microsoft Online Sign-in Assistant is used. Server refuses modern authentication when Skype for Business Online tenants are not enabled. | Microsoft Online Sign-in Assistant only. |
See also
If you have a Microsoft Exchange account, you can look up the schedule of someone in your organization.
The easiest way to see someone's schedule is to start a meeting invitation. After reviewing the person's schedule, you can close the meeting invitation without sending it.
Click Calendar in the Navigation Bar, and then click Meeting on the Home tab.
If you have more than one account in Outlook, on the From menu, select the Exchange account for the organization that you want.
On the To line of the new meeting, type the name or email address of the person whose schedule you want to look up.
Select their name from the Directory section of the search.
In the Starts field, enter the day for which you want to check the schedule.
On the Organizer Meeting tab, click Scheduling.
A calendar appears that shows the free/busy times for the organizer and the person on the To line.
To show all the hours in the day—not just the hours of your work day—clear the Show work hours only check box.
To delete the meeting without sending a meeting request, close the meeting window and choose Discard Invitation.
When you look up other people's schedules, the information you see reflects how they have set their free/busy status for each calendar event. If someone has a meeting on his or her calendar set to Show As 'Free,' you will not see that meeting in the calendar window.
This procedure instructs you to set up a meeting invitation. However, you can then delete the invitation without sending it.
On the Home tab, click New, and then click Meeting.
In the To box, type the name or address of the person whose schedule you want to look up.
If you have more than one account in Outlook, on the From menu, select the Exchange account for the organization that you want.
In the Starts field of the meeting, enter the day for which you want to check the schedule.
Click the Scheduling Assistant tab, which is located under the date and time text boxes.
A calendar appears that indicates the free/busy times for the person in the To box.
To show all the hours in the day — not just the hours of your work day — clear the Show work hours only check box.
Sep 25, 2017 The issue is with Microsoft's software which does not have the right access permissions set up on Mac OS X. Microsoft has to update their software for this set of devices and make it compatible with Mac OS X El Captain (10.11.1) in order for the Sculpt ergonomic desktop set to work. Microsoft sculpt ergonomic keyboard problem. May 20, 2019 Microsoft Sculpt Ergonomic keyboard + Mac. Thread starter navaira; Start date Aug 7, 2015; Sort (Likes) Forums. (some of the function keys not working etc.). I found that when I had the USB dongle attached the back of my mac mini and the keyboard was on an ergonomic tray under my desk and outside of the 'line of sight' from the computer.
To delete the event without sending it, close the meeting window.
Tip: When you look up someone else's schedule, the information that you see reflects how they have set their free/busy status for each event. If someone has marked a meeting status as 'Free,' you will not see that meeting on their calendar.