Топфейс мобильная версия войти через профиль одноклассники: Знакомства Topface | Общайся, встречайся, заводи друзей

ТопФейс — мобильная версия популярного сайтазнакомств

В эпоху информационного простора старые способы знакомств вызывают лишь недоумение, сейчас же отлично подходит ТопФейс, мобильная версия которого выросла из небольшого приложение для знакомств в самую настоящую индустрию.

Отличительные черты и направленность

Ранее всегда смотрели на оболочку, а провожали – по интеллектуальным способностям. Сегодня проект, у которого нет мобильной версии сайта, сразу же попадает в число «не популярных». Поэтому создатели сервиса Топфейс разработали приложение для телефонов и портативных девайсов.

После перехода на мобильную версию программа стала способна похвастаться большим количеством участников: более 45 миллионов зарегистрированных человек.

Разумеется, без процедуры регистрации пользователя не допустят к персональным знакомствам и фотографиям.

Возможности мобильного приложения ТопФейс

«Topface знакомства и общение» — мобильная версия доступна для скачивания в Плей Маркете. Можно зайти, используя учетную запись Фейсбук или ВК. Необычно то, что можно регистрироваться через ВК – это могут делать лишь те, кто используют мобильную версию, на основном веб-ресурсу такая возможность отключена. Также можно войти через Mail.

После регистрации юзер переместится в меню аккаунта, где можно указать:

• небольшое описание себя, рост;
• вес, возраст;
• добавить личное фото, многое другое.

Используя этот профиль, человек сможет войти и начать знакомиться в Топфейс. Грамотные подсказки не позволят потеряться в различных разделах сервиса.

Что касается денежных символов: здесь имеются платные функции. Разумеется, у этого проекта есть платные функции. Если человеку кажется, будто окружающие люди недооценили его профиль, то можно заплатить разработчикам сервиса и тогда его фотографии окажутся в топе, где их посмотрит намного больше участников.

Такая программа подразумевает приобретение «энергии» за монеты – внутреннюю валюту. Удовольствие недорогое, к примеру, за 3 доллара можно отправить личный аккаунт к вершине рейтинга.

Оформление мобильного клиента Topface

Несмотря на то, что интерфейс стандартно выполнен на английском (хотя имеется возможность взаимодействовать с программой на русском языке) – разобраться с ним сможет даже новичок. В основном меню есть 6 вкладок, нажав на любую из них, откроется новый режим или раздел.

Кликнув на клавишу «Поиск», удастся зайти в профили пользователей, в частности посмотреть их фото, которые можно «пролайкать», кликнув на сердечко. Если между двумя участниками возникнет симпатия, это отобразится в разделе «Обоюдная заинтересованность».

Имеется мгновенный переход к людям, которым понравились фотографии пользователя — достаточно использовать вкладку «Моя страница» — «Кому вы понравились».

Проект имеет некоторые недостатки. Например, отсутствует кнопка «Игнорировать», к тому же, нежелательных участников нельзя заблокировать. От навязчивого собеседника отделаться не получится.

Интересные особенности мобильной версии Топфейс

ТопФейс — мобильная версия его разрешает передавать мгновенные текстовые послание через раздел «Мои сообщения». Помимо этого, удастся узнать перечень тех, кто смотрел профиль пользователя (вкладка «Гости»).
Приложение обладает некоторой системой фильтров. К примеру, стандартно отображаются фотографии участников из одного города. Можно корректировать поиск по полу, местоположение и возрасту. Мобильная версия сайта также доступна по адресу m.topface.com

90000 Topface Sign Up — Topface Login — Topface Dating Site Registration 90001 90002 90003 Topface Sign Up — Topface Login 90004 — Are you looking to join an international online dating site that allows you find interesting people, girls, and guys and singles of categories, with similar interests and hobbies all around the world. Then complete Topface sign up or Create Topface Account and also learn the process of Topface login to meet with friends and more especially new friends, keep in touch and communicate at any time.90005 90002 To register Topface account and complete Topface login is free, which means you do not have to pay money to complete the Account set up. It is completely free and lets you hook up with new people on the go. 90005 90002 With over 100 million people from all around the world on Topface online dating, it is incredible, and matching up with people you are interested in becomes more easier. There is everything to benefit when you join in quest for a date. 90005 90010 90011 Also Read — Jaumo Online Dating Site Account Registration 90012 90013 90002 Join by creating an account, and you can decide to Sign in with VK, Sign in with Facebook.Even Topface login with Ok.ru is possible and you can also sign in with Mail.ru just with whichever one you like. 90005 90002 In this article, just right below, we have designed for you the step by step guide to create Topface account. It is easy and simple, thus let’s get started with the whole process of Topface Sign Up — Topface Login. 90005 90018 Topface Sign Up — How To Create Topface Online Dating Account 90019 90002 90003 1. 90004 Go to Topface 90003 Sign up Page 90004 — At the Homepage, Locate 90003 «Create a profile» 90004 below 90005 90002 90003 2.90004 Click on Create «Create a profile» — And A pop up form will appear 90005 90002 90003 3. 90004 Enter your names (90003 First name 90004) 90005 90002 90003 4. 90004 Enter your 90003 Email and Password >> See How To Create Email Account 90042 90004 90005 90002 90003 5. 90004 Select your 90003 Date of Birth 90004 90005 90002 90003 6. 90004 Type in your city 90003 (Location) 90004 90005 90002 90003 7. 90004 Click the 90003 «Sign up» 90004 Button to complete your 90003 Topface Registration 90004 90005 90002 And now you may be automatically logged in after complete the 90003 Topface account registration 90004.But what happens when you decide to log in again in future? This has also prompted us into showing you how you can log in or sign in your 90003 Topface account. 90004 90005 90010 90072 People Also Create Zoosk Online Dating Account 90073 90013 90002 The steps are simple, and see them below; 90005 90002 90003 N | B: 90004 Topface login or Topface sign in has other alternatives like Topface Sign in with VK, Topface Sign in with facebook, Topface Sign in with Ok.ru and Topface Sign in with Mail.ru. We are going to discuss them all separately. Thus let’s get started; 90005 90081 90018 Topface Login — How To Sign In Topface Account 90019 90002 90003 1. 90004 Go to Topface Login Page here http://topface.com/ 90042 At the Homepage, Locate «Do you already have an account?» Sign in 90005 90002 90003 2. 90004 Click on the «Sign in» 90042 A pop up form will appear 90005 90002 90003 3. 90004 Enter your email or phone number 90005 90002 90003 4. 90004 Enter your Password 90005 90002 90003 5.90004 Click the «Login» Button to enter your dashboard / profile page at once 90005 90010 90011 How To Create Yahoo Mail Account For Free 90012 90013 90110 90011 Topface Sign in with VK — How to Sign in Topface Dating Account with VK 90012 90002 90003 Topface Sign in 90004 with VK is very simple and can be done only when you have a VK account. After creating VK Account, follow the steps below to Sign in Topface with VK. 90005 90002 90003 1. 90004 With your browser go to 90003 Topface website 90004 at http: // topface.com / 90005 90002 90003 2. 90004 At the homepage, locate «Sign in with VK» Towards the buttoN of the page 90005 90002 90003 3. 90004 Click «Sign in with VK» 90005 90002 90003 4. 90004 Enter your email and password 90005 90002 90003 5. 90004 Click the login button 90005 90011 Topface Sign in with Facebook — How to Sign in Topface With Facebook Account 90012 90002 If you want to use this method to sign in Topface, follow the steps below to Sign in Topface With Facebook Account 90005 90010 90011 Do not Have a Facebook Account? See How To Create Facebook Account 90012 90013 90002 90003 1.90004 With your browser go to Topface website at http://topface.com/ 90005 90002 90003 2. 90004 At the homepage, locate «90003 Sign in with facebook 90004» Towards the bottom of the page 90005 90002 90003 3. 90004 Click «Sign in with facebook» 90005 90002 90003 4. 90004 If you are already logged to your Facebook account — Continue as your name 90005 90002 90003 5. 90004 If you are not logged in, then enter your Facebook login details to 90003 login Topface with Facebook. 90004 90005 90002 And the procdeure is same for the other methods of signing in Topface dating account.But you must have created an account with VK, Facebook, OK.ru, Mail.ru before you will be able to login Topface with any of them. 90005 90110 90011 Topface App Download For Mobile Phones 90012 90002 This is one of the most interesting part of it, because when you 90003 download Topface dating app 90004, it becomes more easier and a lot convenient to meeting people on the Topface platform. 90005 90002 You get notifications on the go, easy access to your account, reach your profile at the tap of the 90003 Topface app 90004 in your mobile phone.90005 90002 To download Topface mobile app is completely free and you can follow the link below; 90005 90072 Download Topface for your Android phone 90073 90072 90003 Download Topface for iOS. 90004 90073 90002 90193 90003 Hope this article was helpful? Do share, and also ask questions, make contributions using the comment box right below. 90004 90196 90005 90011 Comments 90012 90002 comments 90005.90000 Get access on behalf of a user — Microsoft Graph 90001 90002 90003 90004 6/23/2020 90005 90006 90003 11 minutes to read 90006 90003 90006 90011 90012 In this article 90013 90014 To use Microsoft Graph to read and write resources on behalf of a user, your app must get an access token from the Microsoft identity platform and attach the token to requests that it sends to Microsoft Graph.The exact authentication flow that you will use to get access tokens will depend on the kind of app you are developing and whether you want to use OpenID Connect to sign the user in to your app. One common flow used by native and mobile apps and also by some Web apps is the OAuth 2.0 authorization code grant flow. This topic walks through an example using this flow. 90015 90016 Authentication and Authorization steps 90017 90014 The basic steps required to use the OAuth 2.0 authorization code grant flow to get an access token from the Microsoft identity platform endpoint are: 90015 90020 90003 Register your app with Azure AD.90006 90003 Get authorization. 90006 90003 Get an access token. 90006 90003 Call Microsoft Graph with the access token. 90006 90003 Use a refresh token to get a new access token. 90006 90031 90016 1. Register your app 90017 90014 To use the Microsoft identity platform endpoint, you must register your app using the Azure app registration portal. You can use either a Microsoft account or a work or school account to register an app. 90015 90014 To configure an app to use the OAuth 2.0 authorization code grant flow, you’ll need to save the following values ​​when registering the app: 90015 90038 90003 The Application (client) ID assigned by the app registration portal. 90006 90003 A Client (application) Secret, either a password or a public / private key pair (certificate). This is not required for native apps. 90006 90003 A Redirect URI (or reply URL) for your app to receive responses from Azure AD. 90006 90011 90014 For steps on how to configure an app in the Azure portal, see Register your app.90015 90016 2. Get authorization 90017 90014 The first step to getting an access token for many OpenID Connect and OAuth 2.0 flows is to redirect the user to the Microsoft identity platform 90051 / authorize 90052 endpoint. Azure AD will sign the user in and ensure their consent for the permissions your app requests. In the authorization code grant flow, after consent is obtained, Azure AD will return an authorization_code to your app that it can redeem at the Microsoft identity platform 90051 / token 90052 endpoint for an access token.90015 90012 Authorization request 90013 90014 The following shows an example request to the 90051 / authorize 90052 endpoint. 90015 90014 With the Microsoft identity platform endpoint, permissions are requested using the 90051 scope 90052 parameter. In this example, the Microsoft Graph permissions requested are for 90065 User.Read 90066 and 90065 Mail.Read 90066, which will allow the app to read the profile and mail of the signed-in user. The 90065 offline_access 90066 permission is requested so that the app can get a refresh token, which it can use to get a new access token when the current one expires.90015 90072 90051 // Line breaks for legibility only https://login.microsoftonline.com/{tenant}/oauth3/v2.0/authorize? client_id = 6731de76-14a6-49ae-97bc-6eba6914391e & Response_type = code & Redirect_uri = http% 3A% 2F% 2Flocalhost% 2Fmyapp% 2F & Response_mode = query & Scope = offline_access% 20user.read% 20mail.read & State = 12345 90052 90075 90076 90077 90078 90079 Parameter 90080 90079 Required 90080 90079 Description 90080 90085 90086 90087 90078 90089 tenant 90090 90089 required 90090 90089 The 90051 {tenant} 90052 value in the path of the request can be used to control who can sign into the application.The allowed values ​​are 90051 common 90052 for both Microsoft accounts and work or school accounts, 90051 organizations 90052 for work or school accounts only, 90051 consumers 90052 for Microsoft accounts only, and tenant identifiers such as the tenant ID or domain name. For more detail, see protocol basics. 90090 90085 90078 90089 client_id 90090 90089 required 90090 90089 The Application ID that the registration portal assigned your app. 90090 90085 90078 90089 response_type 90090 90089 required 90090 90089 Must include 90051 code 90052 for the authorization code flow.90090 90085 90078 90089 redirect_uri 90090 90089 recommended 90090 90089 The redirect_uri of your app, where authentication responses can be sent and received by your app. It must exactly match one of the redirect_uris you registered in the app registration portal, except it must be URL encoded. For native and mobile apps, you should use the default value of 90051 https://login.microsoftonline.com/common/oauth3/nativeclient 90052. 90090 90085 90078 90089 scope 90090 90089 required 90090 90089 A space-separated list of the Microsoft Graph permissions that you want the user to consent to.This may also include OpenID scopes. 90090 90085 90078 90089 response_mode 90090 90089 recommended 90090 90089 Specifies the method that should be used to send the resulting token back to your app. Can be 90051 query 90052 or 90051 form_post 90052. 90090 90085 90078 90089 state 90090 90089 recommended 90090 90089 A value included in the request that will also be returned in the token response. It can be a string of any content that you wish. A randomly generated unique value is typically used for preventing cross-site request forgery attacks.The state is also used to encode information about the user’s state in the app before the authentication request occurred, such as the page or view they were on. 90090 90085 90160 90161 90162 90014 90164 Important 90165: Microsoft Graph exposes two kinds of permissions: application and delegated. For apps that run with a signed-in user, you request delegated permissions in the 90051 scope 90052 parameter. These permissions delegate the privileges of the signed-in user to your app, allowing it to act as the signed-in user when making calls to Microsoft Graph.For more detailed information about the permissions available through Microsoft Graph, see the Permissions reference. 90015 90169 90012 Consent experience 90013 90014 At this point, the user will be asked to enter their credentials to authenticate with Microsoft. The Microsoft identity platform v2.0 endpoint will also ensure that the user has consented to the permissions indicated in the 90051 scope 90052 query parameter. If the user has not consented to any of those permissions and if an administrator has not previously consented on behalf of all users in the organization, they will be asked to consent to the required permissions.90015 90014 The following is an example of the consent dialog box presented for a Microsoft account user. 90015 90014 90015 90162 90014 90164 Try 90165 If you have a Microsoft account or an Azure AD work or school account, you can try this for yourself by clicking the following link. After signing in, your browser should be redirected to 90051 https: // localhost / myapp / 90052 with a 90051 code 90052 in the address bar. 90015 90014 https://login.microsoftonline.com/common/oauth3/v2.0 / authorize … 90015 90169 90012 Authorization response 90013 90014 If the user consents to the permissions your app requested, the response will contain the authorization code in the 90051 code 90052 parameter. Here is an example of a successful response to the previous request. Because the 90051 response_mode 90052 parameter in the request was set to 90051 query 90052, the response is returned in the query string of the redirect URL. 90015 90072 90051 GET https: // localhost / myapp /? code = M0ab92efe-b6fd-df08-87dc-2c6500a7f84d & State = 12345 90052 90075 90076 90077 90078 90079 Parameter 90080 90079 Description 90080 90085 90086 90087 90078 90089 code 90090 90089 The authorization_code that the app requested.The app can use the authorization code to request an access token for the target resource. Authorization_codes are very short lived, typically they expire after about 10 minutes. 90090 90085 90078 90089 state 90090 90089 If a state parameter is included in the request, the same value should appear in the response. The app should verify that the state values ​​in the request and response are identical. 90090 90085 90160 90161 90016 3. Get a token 90017 90014 Your app uses the authorization 90051 code 90052 received in the previous step to request an access token by sending a 90051 POST 90052 request to the 90051 / token 90052 endpoint.90015 90012 Token request 90013 90072 90051 // Line breaks for legibility only POST /{tenant}/oauth3/v2.0/token HTTP / 1.1 Host: https://login.microsoftonline.com Content-Type: application / x-www-form-urlencoded client_id = 6731de76-14a6-49ae-97bc-6eba6914391e & Scope = user.read% 20mail.read & Code = OAAABAAAAiL9Kn2Z27UubvWFPbm0gLWQJVzCTE9UkP3pSx1aXxUjq3n8b2JRLk4OxVXr … & Redirect_uri = http% 3A% 2F% 2Flocalhost% 2Fmyapp% 2F & Grant_type = authorization_code & Client_secret = JqQX2PNo9bpM0uEihUPzyrh // NOTE: Only required for web apps 90052 90075 90076 90077 90078 90079 Parameter 90080 90079 Required 90080 90079 Description 90080 90085 90086 90087 90078 90089 tenant 90090 90089 required 90090 90089 The 90051 {tenant} 90052 value in the path of the request can be used to control who can sign into the application.The allowed values ​​are 90051 common 90052 for both Microsoft accounts and work or school accounts, 90051 organizations 90052 for work or school accounts only, 90051 consumers 90052 for Microsoft accounts only, and tenant identifiers such as the tenant ID or domain name. For more detail, see protocol basics. 90090 90085 90078 90089 client_id 90090 90089 required 90090 90089 The Application ID that the registration portal) assigned your app. 90090 90085 90078 90089 grant_type 90090 90089 required 90090 90089 Must be 90051 authorization_code 90052 for the authorization code flow.90090 90085 90078 90089 scope 90090 90089 required 90090 90089 A space-separated list of scopes. The scopes requested in this leg must be equivalent to or a subset of the scopes requested in the first (authorization) leg. If the scopes specified in this request span multiple resource servers, then the v2.0 endpoint will return a token for the resource specified in the first scope. 90090 90085 90078 90089 code 90090 90089 required 90090 90089 The authorization_code that you acquired in the first leg of the flow.90090 90085 90078 90089 redirect_uri 90090 90089 required 90090 90089 The same redirect_uri value that was used to acquire the authorization_code. 90090 90085 90078 90089 client_secret 90090 90089 required for web apps 90090 90089 The application secret that you created in the app registration portal for your app. It should not be used in a native app, because client_secrets can not be reliably stored on devices. It is required for web apps and web APIs, which have the ability to store the client_secret securely on the server side.90090 90085 90160 90161 90012 Token response 90013 90014 Although the access token is opaque to your app, the response contains a list of the permissions that the access token is good for in the 90051 scope 90052 parameter. 90015 90072 90051 { «Token_type»: «Bearer», «Scope»: «user.read% 20Fmail.read», «Expires_in»: 3600 «Access_token»: «eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ik5HVEZ2ZEstZnl0aEV1Q …», «Refresh_token»: «AwABAAAAvPM1KaPlrEqdFSBzjqfTGAMxZGUTdM0t4B4… » } 90052 90075 90076 90077 90078 90079 Parameter 90080 90079 Description 90080 90085 90086 90087 90078 90089 token_type 90090 90089 Indicates the token type value. The only type that Azure AD supports is Bearer. 90090 90085 90078 90089 scope 90090 90089 A space separated list of the Microsoft Graph permissions that the access_token is valid for. 90090 90085 90078 90089 expires_in 90090 90089 How long the access token is valid (in seconds). 90090 90085 90078 90089 access_token 90090 90089 The requested access token.Your app can use this token to call Microsoft Graph. 90090 90085 90078 90089 refresh_token 90090 90089 An OAuth 2.0 refresh token. Your app can use this token to acquire additional access tokens after the current access token expires. Refresh tokens are long-lived, and can be used to retain access to resources for extended periods of time. For more detail, refer to the v2.0 token reference. 90090 90085 90160 90161 90016 4. Use the access token to call Microsoft Graph 90017 90014 After you have an access token, you can use it to call Microsoft Graph by including it in the 90051 Authorization 90052 header of a request.The following request gets the profile of the signed-in user. 90015 90072 90051 GET https://graph.microsoft.com/v1.0/me Authorization: Bearer eyJ0eXAiO … 0X2tnSQLEANnSPHY0gKcgw Host: graph.microsoft.com 90052 90075 90014 A successful response will look similar to the following (some response headers have been removed). 90015 90072 90051 HTTP / 1.1 200 OK Content-Type: application / json; odata.metadata = minimal; odata.streaming = true; IEEE754Compatible = false; charset = utf-8 request-id: f45d08c0-6901-473a-90f5-7867287de97f client-request-id: f45d08c0-6901-473a-90f5-7867287de97f OData-Version: 4.0 Duration: 727.0022 Date: Thu, 20 Apr 2017 5:21:18 GMT Content-Length: 407 { «@ Odata.context»: «https://graph.microsoft.com/v1.0/$metadata#users/$entity», «Id»: «12345678-73a6-4952-a53a-e9916737ff7f», «BusinessPhones»: [ «+1 555555555» ], «DisplayName»: «Chris Green», «GivenName»: «Chris», «JobTitle»: «Software Engineer», «Mail»: null, «MobilePhone»: «+ 1 5555555555», «OfficeLocation»: «Seattle Office», «PreferredLanguage»: null, «Surname»: «Green», «UserPrincipalName»: «ChrisG @ contoso.onmicrosoft.com » } 90052 90075 90016 5. Use the refresh token to get a new access token 90017 90014 Access tokens are short lived, and you must refresh them after they expire to continue accessing resources. You can do so by submitting another 90051 POST 90052 request to the 90051 / token 90052 endpoint, this time providing the 90051 refresh_token 90052 instead of the 90051 code 90052. 90015 90012 Request 90013 90072 90051 // Line breaks for legibility only POST / common / oauth3 / v2.0 / token HTTP / 1.1 Host: https://login.microsoftonline.com Content-Type: application / x-www-form-urlencoded client_id = 6731de76-14a6-49ae-97bc-6eba6914391e & Scope = user.read% 20mail.read & Refresh_token = OAAABAAAAiL9Kn2Z27UubvWFPbm0gLWQJVzCTE9UkP3pSx1aXxUjq … & Redirect_uri = http% 3A% 2F% 2Flocalhost% 2Fmyapp% 2F & Grant_type = refresh_token & Client_secret = JqQX2PNo9bpM0uEihUPzyrh // NOTE: Only required for web apps 90052 90075 90076 90077 90078 90079 Parameter 90080 90079 Required 90080 90079 Description 90080 90085 90086 90087 90078 90089 client_id 90090 90089 required 90090 90089 The Application ID that the registration portal assigned your app.90090 90085 90078 90089 grant_type 90090 90089 required 90090 90089 Must be 90051 refresh_token 90052. 90090 90085 90078 90089 scope 90090 90089 required 90090 90089 A space-separated list of permissions (scopes). The permissions requested must be equivalent to or a subset of the permissions requested in the original authorization_code request. 90090 90085 90078 90089 refresh_token 90090 90089 required 90090 90089 The refresh_token that you acquired during the token request.90090 90085 90078 90089 redirect_uri 90090 90089 required 90090 90089 The same redirect_uri value that was used to acquire the authorization_code. 90090 90085 90078 90089 client_secret 90090 90089 required for web apps 90090 90089 The application secret that you created in the app registration portal for your app. It should not be used in a native app, because client_secrets can not be reliably stored on devices. It is required for web apps and web APIs, which have the ability to store the client_secret securely on the server side.90090 90085 90160 90161 90012 Response 90013 90014 A successful token response will look similar to the following. 90015 90072 90051 { «Access_token»: «eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsIng1dCI6Ik5HVEZ2ZEstZnl0aEV1Q …», «Token_type»: «Bearer», «Expires_in»: 3599, «Scope»: «user.read% 20mail.read», «Refresh_token»: «AwABAAAAvPM1KaPlrEqdFSBzjqfTGAMxZGUTdM0t4B4 …», } 90052 90075 90076 90077 90078 90079 Parameter 90080 90079 Description 90080 90085 90086 90087 90078 90089 access_token 90090 90089 The requested access token.The app can use this token in calls to Microsoft Graph. 90090 90085 90078 90089 token_type 90090 90089 Indicates the token type value. The only type that Azure AD supports is Bearer 90090 90085 90078 90089 expires_in 90090 90089 How long the access token is valid (in seconds). 90090 90085 90078 90089 scope 90090 90089 The permissions (scopes) that the access_token is valid for. 90090 90085 90078 90089 refresh_token 90090 90089 A new OAuth 2.0 refresh token. You should replace the old refresh token with this newly acquired refresh token to ensure your refresh tokens remain valid for as long as possible.90090 90085 90160 90161 90016 Supported app scenarios and additional resources 90017 90014 You can call Microsoft Graph on behalf of a user from the following kinds of apps: 90015 90014 For more information about supported app scenarios with the Microsoft identity platform endpoint, see App scenarios and authentication flows. 90015 90162 90014 90164 Note 90165: Calling Microsoft Graph from a standalone web API is not currently supported by the Microsoft identity platform endpoint.For this scenario, you need to use the Azure AD endpoint. 90015 90169 90014 For more information about getting access to Microsoft Graph on behalf of a user from the Microsoft identity platform endpoint: 90015 90016 Endpoint considerations 90017 90014 Microsoft continues to support the Azure AD endpoint. There are several differences between using the Microsoft identity platform endpoint and the Azure AD endpoint. When using the Azure AD endpoint: 90015 90038 90003 Your app will require a different application ID (client ID) for each platform.90006 90003 If your app is a multi-tenant app, you must explicitly configure it to be multi-tenant at the Azure portal. 90006 90003 All permissions that your app needs must be configured by the developer. The Azure AD endpoint does not support dynamic (incremental) consent. 90006 90003 The Azure AD endpoint uses a 90051 resource 90052 parameter in authorization and token requests to specify the resource, such as Microsoft Graph, for which it wants permissions. The endpoint does not support the 90051 scope 90052 parameter.90006 90003 The Azure AD endpoint does not expose a specific endpoint for administrator consent. Instead apps use the 90051 prompt = admin_consent 90052 parameter in the authorization request to obtain administrator consent for an organization. For more information, see 90164 Triggering the Azure AD consent framework at runtime 90165 in Integrating applications with Azure Active Directory. 90006 90011 90014 For more information about getting access to Microsoft Graph on behalf of a user from the Azure AD endpoint: 90015 90038 90003 For information about using the Microsoft identity platform endpoint with different kinds of apps, see the 90164 Get Started 90165 links in the Microsoft identity platform developer documentation.The documentation contains links to overview topics, quickstarts, tutorials, code samples and protocol documentation for different kinds of apps supported by the Microsoft identity platform endpoint. 90006 90003 For information about the Microsoft Authentication Library (MSAL) and server middleware available for use with the Microsoft identity platform endpoint, see Microsoft Authentication Libraries. 90006 90011 .