I have an application that uses the Microsoft Graph API to read and write emails from a mailbox.
I'm making a request to URL
GET https://graph.microsoft.com/v1.0/users/{user_id}/mailFolders/PublicFoldersRoot/childFolders
This used to work, but since April 2021 it broke and now returns an error
{
"error": {
"code": "ErrorMailboxMoveInProgress",
"message": "Mailbox move in progress. Try again later., Cross Server access is not allowed for mailbox UUID"
}
}
No mailboxes have been initiated to move in my account.
I found the same thread on this issue, but there is no solution yet. Mailbox move in progress.
I didn't find out any workaround. Please help if you know how to fix this.
Apologies for the inconvenience caused to you.
Could you please check if there are any mailboxes being moved?
You can use Poweshell Cmdlet Get-MoveRequest to check if there are any active requests.
If there aren't any, this could be an intermittent issue and should resolve itself without your intervention
However, if this is critical and affecting your production workloads, please reach out to Support as it would be difficult to debug this remotely.
You can also check if there are any service issues affecting your subscription from the Service Health page
Hope this helps. Thanks!
Related
I am follow the tutorial that Microsoft has provided for signing a user into a desktop application using Microsoft Identity Platform and calling ASP.NET Core Web API which calls Microsoft Graph. I believe I followed all of the steps, configuring my service and client per instructions. https://github.com/Azure-Samples/active-directory-dotnet-native-aspnetcore-v2/tree/master/2.%20Web%20API%20now%20calls%20Microsoft%20Graph
However upon trying to add a new "to-do", I get the following error: "Bad Request: An error occurred while calling the downstream API Code:InvalidAuthenticationToken
Message: Invalid x5t claim "
The error occurs on this call:
User user = _graphServiceClient.Me.Request().GetAsync().GetAwaiter().GetResult();
Any idea what the issue might be and how I troubleshoot?
Update: I am in the middle of troubleshooting this now with an admin. I am not getting roles back but he is and we now both agree the issue is on the azure application configuration, not the code... frustrating, but we are at least making progress.
Would you please try pasting the token into jwt.ms to decode it and inspect the claims?
I got a similar error due to a lack of access. Changing Delegated and Application Permission for Users solved the issue. You can try that.
Earlier i asked this question, where #Dev helped me. Now when i tried doing to Delegated permissions, its again throwing HTTP error 403. Application permission works for me. Only looks like issue with delegated permission. Strange? Any inputs will be of help.
#Alice, I see that you're using delegated permission scenario. If yes, then you need to allow apps to read service usage reports on behalf of a user. I would suggest you to work with your tenant administrator. They should have assigned the user the appropriate Azure AD limited administrator role - its needed, apart from the permissions that you specify in your code.
I tried the above in past and helped; so give a try. If you still face issues let me know. For more info you can refer the related document.
I created standalone application on node.js authorized in AAD with client/secret with permissions to access groups, sites, directories. I managed to create Teams group and team by Microsoft Graph API but when I tried to fetch sites/root or drives
https://graph.microsoft.com/v1.0/groups/{groupId}/sites/root
https://graph.microsoft.com/v1.0/groups/{groupId}/drive
I received 500 Internal Server Error:
{
"error": {
"code": "generalException",
"message": "An unspecified error has occurred.",
"innerError": {
"request-id": (....),
"date": "2020-01-31T09:15:17"
}
}
}
Is access to sites and drives possible by Graph API with app token?
the error is causing by using "Group.Create","Group.ReadWrite.All" together
Yes it is possible. One possibility here is that if you are attempting to access the drive or site right after creating the team, they may not be provisioned yet. There is some delay that can happen, typically only a few minutes at most.
When you register your Azure Active Directory App, which supported account type are you choosing?
I had exactly the same issue as you, but I've created a new Azure AD App and changed the supported Account type back to the first option and all worked accordingly.
I hope this could help your issue.
Thank you.
Using Microsoft Graph I am successfully creating subscriptions, but when calling HTTP Patch to https://graph.microsoft.com/v1.0/subscriptions/ with a correct (works through Graph Explorer) json payload of
{ "expirationDateTime": "UTCTIME 2 minutes past current expiration"}
I always get 403 Forbidden as a result.
I have the permissions set (I think) correctly to Files.ReadWrite as per https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/api/subscription_update. These should be the same permissions as Creating the subscription so can someone help as to why I can create but not update?
The problem you reported should be fixed now. Please let me know if you're still seeing 403s on subscription update requests.
You should set the permission on project config but not only the apps.dev.microsoft or azure app portal.
If you not sure which config file to set, just get started from the official sample code, or just find the keywords "GraphScope" in your project and add the Files.ReadWrite.All.
You get 403 mainly caused by some wrong config. Still need to check on your side. We can just provide the suggestion to assist you.
I am using Paypal REST api to create subscription plan and subscription agreement. I am able to create subscription plan and credit card but not able to create agreement. Whenever I request it gives internal server error.
I am using ruby gem paypal-sdk-rest
Credit card I am using is
4012888888881881
And mode is Sandbox
the Response I am getting is
Response code = 500. Response message = Internal Server Error.
Response debug ID = ea61a34e9fa73
Thanks in Advance
It happens because of frequently used test Credit Card like the one you are using, if you are use different one for this it will help you to solve this issue...
Or may be below one cause of the error
Sandbox Personal Account being used was invalid. The sandbox personal account is causing all this error 500.
HTTP 500 is caused by an internal error. One of the possible root causes is what JIGNESH mentioned.
Can you please open a Github issue with the information you provided here? It is a better place to discuss this kind of issue.
Also, would you explain how you are using subscription? Ruby REST SDK does not yet support the feature, although it is coming soon. Did you add it yourself?