As per the MS forum https://techcommunity.microsoft.com/t5/exchange-team-blog/outlook-rest-api-beta-and-outlook-rest-api-v2-0-deprecation/ba-p/1898162, Exchange app permission "full_access_as_app" has been removed from the Azure portal. We are using this permission to access\fetch MSTeams data via Exchange Web Service API. We are planning to switch to Graph API from EWS but on Graph API, the chat list API not being supported, we could not switch to it.
That permission being removed - will it impact our existing app? I mean, our Azure Portal App uses this permission and our customers have already granted the consents so will that change impact our customer? Is there any timeline when that Exchange permission will be deprecated or will stop working? Is there any other alternative to this permission as a workaround?
The main reason for asking this question is: just recently MS has deprecated Basic Authentication to EWS so we switched to Modern Authentication (Oauth 2.0) to connect EWS where we had to use that Exchange app permission "full_access_as_app".
Now, that permission is not available for the newly created Azure App. Is this a move towards moving away from EWS and switching to Graph API?
The permissions are still available for new apps (even in the Azure portal if you go though API my organization uses and select "Office365 Exchange Online"). Also in the documentation link in that article https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-authenticate-an-ews-application-by-using-oauth they give a manual way of doing this through the manifest.
Now, that permission is not available for the newly created Azure App. Is this a move towards moving away from EWS and switching to Graph API?
Microsoft have been encouraging this move for quite a while (years) but no announcement have been made about the depreciation of EWS and given that for a lot of things (Migrations etc) there is no alternative in the Graph yet it won't be in the near future. And if it does eventually happen you should get at least a year or more notice. That said if you can use the Graph API you should be looking to move to it.
Related
I'm developing some automation/integration between a CRM software and my google account. I am attempting to use the Google Apps Script API so I can remotely execute functions in Google Apps Script through the integration I'm building from within the CRM software.
The only problem is, when attempting to run a function which calls a GAS function through the API, I get the following error:
"Apps Script API has not been used in project project number before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/script.googleapis.com/overview?project=103424032563 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry."
This would normally be no problem, as I would simply access the GCP portal through the link and enable the GAS API, but when I try to access my project, I don't have access at all, and get the "failed to load data" error.
Further complicating my issue, GCP support will not help because they suspect I am a hacker trying to obtain access to a project that, for all they know, isn't mine.
And because I cannot access this project to authorize the API, I also cannot associate my google script with the same project, as this is a requirement for the Google Apps Script API to function.
I suspect it's the CRM software piece in which I'm developing this integration that is causing this error, (somehow the GCP project is being created by a different user,) but they haven't been all that helpful in determining what's going on.
Have any of you had a similar situation? And, if so, how did you approach solving it?
Further complicating my issue, GCP support will not help because they
suspect I am a hacker trying to obtain access to a project that, for
all they know, isn't mine.
Google Support does not refuse to help. They don't accuse you of being a hacker. Google Support can look at the project and see if you have credentials in the project and if you do they can explain how to authorize yourself. However, Google Support requires a support agreement, which is not free. If you do not have one, then you are not entitled to technical support only billing support. Look up your billing account ID and send a request for billing support. Your billing account will also show you which projects are linked to your billing account.
The issue is that you are trying to access the wrong Project ID. Figure out what is the correct Project ID. If you have the Cloud SDK installed execute this command gcloud projects list and this will tell you which projects your credentials have access to.
We have used CloudRail to retrive files from OneDrive, Google Drive, Amazon S3 and Dropbox without hassle.
When we have tried to implement OneDrive For Business, we get an error
'The app ID is blocked for access of the O365 Discovery Service'
Does anyone know if this error comes from CloudRail or Azure? If I check the Azure history for the application, it is logging that my sign-n status is successful.
We have had multiple developers go through the setup instructions and get the client ID and secret with the same result.
We have now scaled our application to the example code on the CloudRail website and still the same problem.
Has anyone managed to get OneDrive For Business working with CloudRail?
If so, does anyone have any suggestions?
Thanks in advance
According to Microsoft, this is due to the O365 Discovery Service being depreciated. Existing application will still work but no new ones will.
CloudRail has updated their SDK to use Microsoft Graph instead of O365 and all is working.
I need an access to google drive sdk to store and retrive data from web-server but when I tried to get the access, as explained in google drive quick start guide, It says to create project, why is that. and How exactly getting access to drive sdk works?
Google provides a mechanism to allow third party apps to access its APIs. The first step of the process requires you to register the application to Google, eg. so it can bill you for certain access volumes. Your app will be accessing the information, eg the Drive files of end users. They will need to grant permission to your app, so this is a second reason why the app must be registered.
In Google parlance, your app is known as a "Project" and you will "create" (ie. register) your project at the Google Cloud Console.
I was developing android application that has backup to google drive feature.
I have used Simple API Access key and it worked like a charm for few weeks.
However, from yesterday, it does not work at all. (cannot list uploaded files and 403 fobidden error when trying to upload new file) I checked Google APIs Console and found out
Simple API Access
Status: Inactive
and Reports is not available and keeps showing popup message "An unexpected error has occurred. We're looking into it."
I googled about this message but there is no solution. (but found several issues related to google cloud SQL)
I was considering to use google drive on commercial level android app and this is very bad...
I wonder what is the problem and how to reactivate api status.
Thanks :)
Unfortunately, because of the security model of the Drive SDK, we need to be sure that an application is who they say they are, which simple access does not give enough assurance of. For a commercial application, this strength of security is great for users.
For a solution, you need to use Google Play Services as outlined in the documentation. We are currently working on a guide to get started with this very quickly on Android, and should be available within the next week.
Maybe I'm missing something but is there a way to build a free app that integrate Google Drive without having the rate limits "per app"?
If you are not going to release the source code (e.g not making easy for other developers to "steal" your application's client ID and secret), you can request more quota from the APIs Console page under the "Quotas" pane.
For open-source project, I would advise in asking the user/developer to create their own API Project from the APIs Console and provide a "wizard" type setup for them to enter the necessary information.