Inconsistency with findmeetingtime graph api response - microsoft-graph-api

We are using FindMeetingTimes to get Office 365 Rooms resources which are available in a given time constraint.
When number of rooms in Office 365 are less then it is working fine even if multiple hits are made simultaneously.
But eg- If i have 48 rooms and hitting this api simultaneously i'm getting random results instead of getting 48.

Just to isolate the issue out of your code i would suggest you to replicate the issue with Microsoft Graph Explorer or POSTMAN and see if you can still repro the issue. If yes, please share the related info - so that the community can help.

Related

Restore Microsoft Teams Channel via Graph API

I have a service which utilises MS Graph API and I'm looking for a way to delete and restore deleted channel(s) using MS Graph API.
To delete a channel I am utilising /teams/{id}/channels/{id} Graph API, however I am struggling to find a way to recover deleted channel.
In the description of above call it is mentioned that data is stored for couple of weeks (21 days since delete) so there should be a way to recover it?
I know it can be done using Teams application, however I would like to do it via Graph API.
I checked below article and Graph documentation but was not able to find suitable solution. Am I missing something or this has not been implemented yet?
https://blogs.technet.microsoft.com/uclobby/2018/08/21/restore-deleted-teams-and-channels-from-microsoft-teams/
https://learn.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0

Access Denied when querying Teams in Microsoft Graph

Whenever I query the Teams endpoint in Microsoft Graph:
GET https://graph.microsoft.com/beta/teams/{id}
I get the following error:
AccessDenied - Failed to execute Skype backend request GetThreadRequest.
The permissions are set according to the documentation. (Group.Read.All - delegated permission)
Querying https://graph.microsoft.com/beta/groups/{id} is working while with the same access token https://graph.microsoft.com/beta/teams/{id} isn't.
I tried it with my own application and in the Graph Explorer. Both ways didnt't work for me. However using Graph Explorer with the sample account is working. Is there maybe another permission needed which is not yet documented?
Currently it's a requirement that the person using the Graph APIs (and the PowerShell cmdlets that use them under the covers) must be a member of the team whose information they are trying to retrieve. This is the second-most popular ask for users of our cmdlets, and we are close to resolving it. We expect this to be fixed by the end of September 2018, with write APIs/commands coming a few weeks later than read APIs/commands.

Reading Group Conversations from Microsoft Graph using an application permission doesn't seem to be supported

We're building a mashup app that allows you to view data and information from multiple sources in one place.
To do this we need to get all conversations in O365 Groups and have been exploring how to build a daemon job.
According to the documentation this should be supported since we have the permissions Group.Read.All and Group.ReadWrite.All.
However it seems like Groups Conversations is an exception to what you can read with an application permission with Microsoft Graph which is mentioned in a small note on the subscriptions page:
We get permissions errors when calling the API with a application permission using a certificate (fetching groups and other data works fine) so this seems to be a limitation.
This also seems to affect fetching threads which doesn't seem to have any notes regarding application permissions at all since we can't fetch those either.
Does anybody know if there is a workaround or if we're doing something wrong here?
(NOTE: This seems to be a related question: Microsoft Graph API : "403 forbidden" error when getting groups conversations but I'd like to have some input from Microsoft on this)
Microsoft confirmed this as being an issue in the Microsoft Graph through our partner programme.
Until fixed by Microsoft this means that there is no good solution except workarounds as of now.

Delta queries not supported on 'users'

I'm trying to use delta queries on my AD and it works perfectly when I try them out through Graph Explorer, but doesn't work at all with my app, I'm getting this:
message=Invalid request. Delta query is not supported by this resource.
My app is an 'old' app, meaning it was registered in Azure to work with old WAAD graph api. Is this why it's not working? Or could this be because of my app lacking some permission that Graph Explorer requires? I can read 'users' without any issues, it's only delta queries I'm having issues with.
The application requests the following permissions:
Access the directory as the signed-in user
Read all users' basic profiles
Sign in and read user profile
Token requests are managed by the library, it's asking for the following scopes: openid profile
If you're using Azure AD Graph then you cannot use /delta queries. AAD Graph API and Microsoft Graph API are entirely distinct APIs. Calls to one are not interchangeable with the other.
If you're looking to leverage /delta you'll have to refactor your application to use Microsoft Graph API.
Had to spend the whole day on this issue, here's what was going on. I was adding this HTTP header to the request (per some sample documentation):
Prefer: outlook.timezone="E. Europe Standard Time"
And that's what was breaking the delta queries request, as soon as I've removed the header - request returned delta data instead of an error. I wish the error could be more descriptive, I wouldn't have to spend so much time figuring this out.

Google Places Api Daily Limit Issue

Hi I have made an app and enable Google Places api for that project.
I create a project on google developer portal and add the key in to my iOS app After that I start to send request to google Api and My search Works very well as I also know that google has per day request limit on each Api
Now today I send Max. 30 request and after that from google Api I was given error that your daily quota is reached which is 1k request / day.
I did not find any solution on any where Kindly help me to solve this problem.
You need to request more quota:
https://developers.google.com/places/uplift
If you reached the quota while testing your app, make sure that you have used the developer key for that purpose.
What kind of Search are you using?
Some types of searches cost more than others.
For example, one of the autocomplete search types, Text Search, has a 10x multiplier. (https://developers.google.com/places/web-service/usage)
Make sure that you look at the usage limits specified for each API/service you are using.
Additionally, if you are looking at your online dashboard you can see the real-time number of requests that have been made / are being made to each API/service by project. This can help debug when these requests may be being made and how many are occurring per call you believe to be making.

Resources