Messenger Connect Scopes

Current information about Live Connect is now available in the Windows Live Developer Center. The information in the following sections is provided for legacy purposes only.

Windows Live Messenger Connect provides access to an authenticated user's resource data by using scopes.

Resources are structured sets of data, such as contacts, photos, profiles, and activities, that are usually stored on the web. Messenger Connect resources are those that are available through Windows Live services such as Windows Live SkyDrive, Windows Live Messenger, and Windows Live Hotmail.

Scopes are permissions that an application requests for access to resource data. For example, a View scope allows read-only access to data such as contacts or photos, and an Update scope allows write access.

Windows Live users control access to all data. An application can access the resources that are specified in a scope only if the user consents. For more information, see Obtaining User Consent. For more information about how your application specifies scopes, see "Specifying Scopes for Your Application" later in this topic.

The Windows Live Developer Services Terms of Use and the Windows Live SDK License Agreement govern your application's use of scopes. When you connect your application by registering it with the Windows Live application management site, scopes are available to your application. To configure your request to Messenger Connect to include these scopes, follow the instructions in "Specifying Scopes for Your Application" later in this topic.

Users of your application must sign in and grant access for your application to use their data. Choose scopes that provide access only to the minimum amount of user data that is required to complete your feature scenario.

The following table provides a list of available scopes.

Resource Scope Access



View public Windows Live activities, including comments and activities that are related to the requesting application.



View and update public Windows Live activities and activities that are related to the requesting application, add comments, and post to the activities feed. Activities that are posted to a feed are visible to the user's friends.



View information about a user and the user's friends, with the exception of email addresses.



View photo albums and videos that the user has uploaded, along with associated tags and comments.

Not supported in the Messenger Connect JavaScript Library.



View profile information, including user status, profile photo, email addresses, and the user's personal information (for example, schools attended).

Real-Time Shared Experiences


Enable an application to sign in (authenticate) its users to access Messenger Connect communication and sharing features.

To specify a scope or list of scopes, use the scope attribute of the Application Control. Access to the resources that are specified in a scope is allowed only if the user consents. For more information, see Obtaining User Consent.

The following example shows how to use the <wl:app> tag to declare a list of scopes on a webpage. This example requests View permission for a Contacts resource, requests View permission for a Profiles resource, and requests sign-in to Windows Live Messenger.


Specify scope when you declare application metadata in JavaScript code. For more information, see Configuring Your Application by Using the App Tag.

Using Your Own Callback Page

An Open Authorization Web Resource Authorization Protocol (OAuth WRAP) callback page is required for each application that is built via Messenger Connect. (You do not need to create a callback page for Microsoft .NET–based applications because you can use the OAuth WRAP handler to specify scopes. For more information, see Integrating the OAuth WRAP Handler.) The callback page must process the verification code that is returned by the Windows Live consent service, acquire an access token, and store the access token and other information as cookies on the client system. For more information, see Building an OAuth WRAP Callback Page.

When an application requests a scope, the user sees the scope during the consent user experience. This review enables the user to grant or deny consent to the application. The typical flow is as follows:

  1. The application specifies a requested scope and provides a sign-in button.
  2. The user clicks the sign-in button to display a consent window.
  3. The user clicks a link in the consent window to view the resources that are requested in the scope.

For more information about the consent window, see Obtaining User Consent.

Each scope provides access to a set of properties that are related to a specific Windows Live user. For a list of the properties that are unavailable to your application, see the Windows Live Developer Center.