You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/rest-api/concepts/migrating-from-live-sdk.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.localizationpriority: Medium
10
10
If you are using the Live SDK or Live Connect APIs to connect to profile, calendar, contacts, or files, your app needs to be updated to maintain functionality.
11
11
12
12
Live SDK and Live Connect APIs have been marked as deprecated for over a year.
13
-
As announced on the [Office Developer blog](https://dev.office.com/blogs), these APIs are now end of life and will no longer be available after **November 1, 2018**.
13
+
As announced on the [Office Developer blog](https://devblogs.microsoft.com/microsoft365dev/), these APIs are now end of life and will no longer be available after **November 1, 2018**.
14
14
15
15
Profile and contacts data will no longer be available from the Live Connect APIs as of **Decmeber 1, 2017**.
16
16
Calendar data has not been available from Live Connect since **June 2017**.
@@ -24,10 +24,10 @@ To continue to integrate with Microsoft services, developers must update their a
24
24
25
25
Similar to the capabilities of Live Connect, Microsoft Graph has a number of resources available depending on the type of user data your app interacts with:
*[Profile and Identity API](https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/resources/users)
33
33
@@ -41,7 +41,7 @@ Microsoft Graph uses a different set of permission scopes than Live Connect.
41
41
To access the Microsoft Graph APIs, your app will need to switch permission scopes.
42
42
This requires your app to prompt the user for consent to sign in and consent to the new permissions.
43
43
44
-
See the [Microsoft Graph permission reference](https://developer.microsoft.com/en-us/graph/docs/concepts/permissions_reference) for the complete details.
44
+
See the [Microsoft Graph permission reference](/graph/permissions-reference) for the complete details.
45
45
46
46
| Live Connect Scope | Microsoft Graph Permission | Description |
Copy file name to clipboardExpand all lines: docs/rest-api/concepts/working-with-cors.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,10 @@ ms.author: JeremyKe
4
4
ms.date: 09/10/2017
5
5
ms.topic: conceptual
6
6
title: CORS support - OneDrive API
7
-
ms.localizationpriority: Medium
7
+
8
+
localization_priority: Normal
9
+
description: Master OneDrive API with CORS for seamless JavaScript integration. Explore sample code, requests, and file downloads. Boost your app's performance.
10
+
8
11
---
9
12
# Using the OneDrive API in JavaScript apps (CORS support)
Copy file name to clipboardExpand all lines: docs/rest-api/getting-started/aad-oauth.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ You provide an access token for every API call via an HTTP header:
36
36
You access the API by sending HTTP requests to a specific endpoint URL.
37
37
The root URL is based on the host name of the server that serves as the REST endpoint.
38
38
You can use the discovery API to find endpoints for Office 365 services.
39
-
For more information see [Common endpoint discovery tasks using the Discovery Service API](https://msdn.microsoft.com/en-us/office/office365/howto/discover-service-endpoints).
39
+
For more information see [Common endpoint discovery tasks using the Discovery Service API](https://msdn.microsoft.com/office/office365/howto/discover-service-endpoints).
40
40
Your root URL appears in the next example, where `{tenant}` comes from your discovered endpoint URL:
41
41
42
42
`https://{tenant}-my.sharepoint.com/_api/v2.0/`
@@ -59,7 +59,7 @@ To sign into OneDrive for Business the first time, your app needs the following
59
59
The following steps will walk you through the requests necessary to get all of these values.
60
60
61
61
The flow follows standard OAuth 2.0 authentication flows and requires calls from a web browser or web-browser control.
62
-
See [Understanding Office 365 app authentication concepts](https://msdn.microsoft.com/en-us/office/office365/howto/common-app-authentication-tasks) for general Office 365 authentication info.
62
+
See [Understanding Office 365 app authentication concepts](https://msdn.microsoft.com/office/office365/howto/common-app-authentication-tasks) for general Office 365 authentication info.
63
63
However, getting all of the required values to use the OneDrive for Business API requires a few additional steps.
64
64
65
65
The code flow for authentication is a three-step process with separate calls to authenticate and authorize the application and to generate an access token to use the OneDrive API.
@@ -90,7 +90,7 @@ GET https://login.microsoftonline.com/common/oauth2/authorize?response_type=code
90
90
|*response_type*| string | Specifies the requested response type. In an authorization code grant request, the value must be code. |
91
91
|*redirect_uri*| string | The redirect URL that the browser is sent to when authentication is complete. |
92
92
93
-
**Note** The redirect URI must match one of the redirect URI that you specified in the [Azure Management Portal](https://manage.windowsazure.com/).
93
+
**Note** The redirect URI must match one of the redirect URI that you specified in the [Azure Management Portal](https://portal.azure.com).
94
94
95
95
#### Response
96
96
@@ -226,7 +226,7 @@ The request body is a URL encoded string, with the following parameters:
226
226
|*resource*| string | The resource you want to access. This should be the previously discovered **serviceResourceId** value. |
227
227
228
228
229
-
**Note** The redirect URI must match the the redirect URI that you specified in the [Azure Management Portal](https://manage.windowsazure.com/).
229
+
**Note** The redirect URI must match the the redirect URI that you specified in the [Azure Management Portal](https://portal.azure.com).
230
230
231
231
#### Response
232
232
@@ -244,7 +244,7 @@ If the call is successful, the response body is a JSON string that including `ac
244
244
**Note:** Replace refresh token values that you have previously stored with those returned from subsequent calls to the token service to ensure that your app has a token with the latest expiration.
245
245
246
246
The value of the **access_token** property can now be used to make authenticated requests to the OneDrive API.
247
-
For more info about refresh tokens, see [Refresh Tokens for Multiple Resources](https://msdn.microsoft.com/en-us/library/azure/dn645538.aspx).
247
+
For more info about refresh tokens, see [Refresh Tokens for Multiple Resources](https://msdn.microsoft.com/library/azure/dn645538.aspx).
248
248
249
249
**Important:** Treat the values of `access_token` and `refresh_token` in this response as securely as you would a user's password.
250
250
@@ -278,7 +278,7 @@ The page content will always display a generic error message for the user.
278
278
279
279
If the user selects not to provide consent to your application, the flow will redirect to your redirect_uri and include the same error parameters.
280
280
281
-
For more info about handling errors, see [Error Handling in OAuth 2.0](https://msdn.microsoft.com/en-us/library/azure/dn645540.aspx).
281
+
For more info about handling errors, see [Error Handling in OAuth 2.0](https://msdn.microsoft.com/library/azure/dn645540.aspx).
Copy file name to clipboardExpand all lines: docs/rest-api/getting-started/app-registration-server.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,33 +63,33 @@ with the name of your Office 365 tenant.
63
63
If you already have an existing Azure AD tenant, you can associate it with
64
64
your Office 365 subscription by following these steps:
65
65
66
-
1. Sign in to the [Microsoft Azure Management](https://manage.windowsazure.com/)
66
+
1. Sign in to the [Microsoft Azure Management](https://portal.azure.com)
67
67
portal with your existing Azure credentials (for example, your Microsoft ID
68
68
such as user@live.com), and navigate to the **Active Directory** node.
69
69
2. Choose the **Active Directory** node, then choose the **Directory** tab and,
70
70
at the bottom of the screen, choose **New**. In the next dialog box, choose **Use
71
71
existing directory**, select the check box, and then choose the check mark in the
72
-
lower-right corner. This brings you back to the [Azure Management Portal](https://manage.windowsazure.com/).
72
+
lower-right corner. This brings you back to the [Azure Management Portal](https://portal.azure.com).
73
73
3. Sign in with your Office 365 subscription information. You will be prompted
74
74
whether to use your directory with Azure.
75
75
4. Choose **Continue** and a screen appears to confirm your action. Now,
76
76
choose **Sign out now**.
77
-
5. Close the browser and open the [portal](https://manage.windowsazure.com/) again.
77
+
5. Close the browser and open the [portal](https://portal.azure.com) again.
78
78
Otherwise, you will get an access denied error.
79
79
6. Sign in again to your Azure subscription (for example, with your Microsoft ID).
80
80
Navigate to the **Active Directory** node and, under **Directory**, you
81
81
should now see your Office 365 subscription.
82
82
83
83
For more info about setting up an Azure AD tenant, see [Set up Azure Active
84
-
Directory access for your Developer Site](https://msdn.microsoft.com/en-us/office/office365/howto/setup-development-environment#bk_CreateAzureSubscription).
84
+
Directory access for your Developer Site](https://msdn.microsoft.com/office/office365/howto/setup-development-environment#bk_CreateAzureSubscription).
85
85
86
86
### 3. Register your app with Azure Active Directory
87
87
88
-
To authenticate your app, you need to register your app with Azure AD, and provide some details about your app. You can register your app manually by using the [Azure Management Portal](https://manage.windowsazure.com/),
88
+
To authenticate your app, you need to register your app with Azure AD, and provide some details about your app. You can register your app manually by using the [Azure Management Portal](https://portal.azure.com),
89
89
or by using Visual Studio.
90
90
91
91
To register your app manually, see [Manually register your app with Azure AD so
92
-
it can access Office 365 APIs](https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually).
92
+
it can access Office 365 APIs](https://msdn.microsoft.com/office/office365/howto/add-common-consent-manually).
93
93
94
94
To register your app by using Visual Studio, see [Using Visual Studio to
95
95
register your app and add Office 365 APIs](https://msdn.microsoft.com/office/office365/HowTo/adding-service-to-your-Visual-Studio-project).
@@ -102,7 +102,7 @@ your access token.
102
102
as you would a user's password. The secret represents the key to your
103
103
application and, if made available, can be used to impersonate your application.
104
104
105
-
When you register your app in the [Azure Management Portal](https://manage.windowsazure.com/),
105
+
When you register your app in the [Azure Management Portal](https://portal.azure.com),
106
106
you will need to configure details about your application with the following steps:
107
107
108
108
1. Specify whether your application is a mobile, desktop, or web application.
@@ -114,7 +114,7 @@ you will need to configure details about your application with the following ste
114
114
tenancy you registered it in, or across multiple tenancies.
115
115
4. For web apps, generate the app secret and its duration.
116
116
5. Specify the permission levels your app requires from the Office 365 API
117
-
applications in Azure using [app permissions](https://msdn.microsoft.com/office/office365/howto/application-manifest).
117
+
applications in Azure using [app permissions](/office/office-365-management-api/get-started-with-office-365-management-apis).
118
118
Using OneDrive API or the file picker requires at least **Read user files**. Uploading, editing, or sharing files
119
119
requires the **Read and write user files** permission.
Copy file name to clipboardExpand all lines: docs/rest-api/getting-started/app-registration.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,9 @@ ms.author: JeremyKe
4
4
ms.date: 09/10/2017
5
5
ms.topic: conceptual
6
6
title: Create an app with Microsoft Graph - OneDrive API
7
-
ms.localizationpriority: High
7
+
localization_priority: Priority
8
+
description: Learn to Register Your App for OneDrive API with Microsoft Graph. Get an Application ID & Secure Your App. Maximize Features with Azure AD.
0 commit comments