I am building an app for a client using the Microsoft Grap API and when I log in with a particular account I get this error:
Request Id: d300b62e-e0a5-4f62-9957-1cc10fd42800
Correlation Id: e1912683-45cb-459e-b631-9706f6cd2479
Timestamp: 2020-04-20T07:51:51Z
Message: AADSTS90033: A transient error has occurred. Please try again.
I have tried 2 other accounts and they work without an error.
Does anyone know how I can resolve this issue or how I can start to work out what the issue might be?
EDIT:
Example of the URL being used to authorise the user
https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=<clientid>&response_type=code&redirect_uri=<local_uri>&response_mode=query&scope=openid%20offline_access%20https%3A%2F%2Fgraph.microsoft.com%2Fuser.read&state=12345
Thanks,
Scott.
For those that come here in the future, the best place to check whether or not the issue is isolated to just you, or is part of a wider issue is the official Microsoft 365 Status Twitter account.
You can also check the Microsoft 365 Service health status page (but this only works if the Microsoft login services are working.) Documentation around how to check the service status is available as part of the official docs.
For Azure-related issues you can check the official Azure Support Twitter account or the Azure status page.
If the issue is localised - then you should raise a support ticket in Azure or Office 365, otherwise wait for a resolution from Microsoft.
Related
I get the error "OrganizationFromTenantGuidNotFound" while trying to access to my inbox messages.
To explain I am trying to develop an app and in this app I need to access my inbox e-mails.
So I try to use the Outlook API and for that I created an APP with all demanded permissions "Email.Read, Email.ReadBasics, Emails.ReadAll...". I have an Office 365 Family subscription, and an active paid azure subscription. My question is why getting my personal information works '/users/{user-id}' but when accessing to emails I got this error ? I read a lot of docs and never get an answer... Maybe my subscription does not get me access to Microsoft Exchange Online License, or due to my old microsoft address "...#live.com" maybe it is not compatible, I dont't know, if someone can help me to clear it out, would be great. Oh, and abviously my Office 365 and Azure account are the same.
I tried, with 'client credentials flow authentication' (which give me the error 'need more privileges'), went back to Authorization Code Flow Atuhentication but then I get the OrganizationFromTenantGuidNotFound error. But only on /messages endpoint, the endpoint users/{user-id} works. Obviously I tried all threads I found, even with an Office 365 Developer account but don't really see the correlation with my problem here.
We are trying to connect an internal application to Sharepoint 365. The goal is to read data from Sharepoint 365 lists and Excel documents. We want to take advantage of the fact we already use OAuthentication and basically our users login with their own Windows credentials. Now, to accomplish that we first need to register an application with Sharepoint which we did using this link:
https://mycompany.sharepoint.com/sites/MySite/_layouts/15/appregnew.aspx
After that we also need to get an authorization code for clients to login with their Windows account. We do that with this URL:
https://mycompany.sharepoint.com/sites/MySite/_layouts/15/OAuthAuthorize.aspx?client_id=14f0e39c-1234-42ea-bed5-ee5c7c834655&scope=List.Read&response_type=code&redirect_uri=https%3A%2F%2Fmysite.mycompany.com%3A9090%2Foauth%2F2.0%2FredirectURL.jsp
When we run that last link we get the error below:
Sorry, something went wrong
There is no claims identity. Please make sure the web application is configured to use Claims Authentication.
TECHNICAL DETAILS
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 367ee69f-5066-0000-e1ef-cee55f7b7000
As you can see, the error is not very helpful. I have done already lots of research and answers vary from lack of higher level of access, to invalid URL request. I have elevated access and the URL is well constructed. Yet the error persist.
So, my question, what is the meaning of the error? Why is not executing?
We logged a Microsoft Premier Support ticket and behold! the problem has been fixed.
My purpose is to create bug in Azure DevOps directly from Azure Application Insight, I am doing to attach the work item (bug) feature available in Azure Application Insight but on clicking Authorize button it give me following error
Authorization token provided through OAuth does not have access to read/write work items for requested uri/project collection/project
for reference please find the below image.
Updates:
I didnt understand what you meant by private browser, and I have full admin access over Azure Portal.
basically I have the https://dev.azure.com/HealthTechnologies/ReportItNow link in which
https://dev.azure.com is the devop url
HealthTechnologies is the organization
ReportItNow is the Project
so in Azure insight workitem section, URL I am putting https://dev.azure.com/HealthTechnologies/ and in project I am putting ReportItNow, I dont know what i am doing wrong.
Still waiting for this glitch to solve.
Oky let me make it more simple, if I want to automatically create bug in Azure DevOps when ever any new exception came in to the Azure
Application Insight How I can get this into real practical.
I solve this when I took a detailed look at the error message url. It's saying that the missing authorization is for https://uri/Project Collection/Project. Based on that, I changed my url from https://dev.azure.com/organization to https://dev.azure.com/ and it worked,
I have created an app on Azure Portal to access some information via Microsoft Graph API but I am not able to add any permissions to it. It was working earlier but not any more. I also tried to register a new app, the app gets register but yet again the permissions could not be added.
As soon as I press the button to add the selected permissions these two popup notifications come up ..
1. Your session will end in a few minutes. You will have to refresh your browser to start a new session.
2. The portal is having issues getting an authentication token. The experience rendered may be degraded.
Additional information from the call to get a token:
Extension: Microsoft_AAD_RegisteredApps
This is happening since last 3 days now. I also searched on Google and found that people had similar issues earlier as well. Though I have raised a ticket on the portal for this but haven't received any reply yet.
Any help here would be very much appreciated. Also is there any way to check any logs on the portal itself. I did try to check the network logs via browser developer tools but they aren't much help.
It seems to be an issue with the Azure Portal for your region.
As #Hury Shen suggested, you should contact Azure Support for further investigation.
See how to open a support ticket on Azure portal.
Seems like there was an issue with my account address. I changed the address to one of US and it worked for me.
#Allen Wu Thanks for the suggestions. I had already asked them about it but no one replied.
I have a logic app with an Office 365 connection. Of course I can authenticate this in the portal manually but I would have to do this every time I deploy from my deployment automation pipeline.
I have found a post of this but it is no longer available:
Authenticating office365 logic app connector with PS
The link that is no longer available
Here is what I mean in the portal:
Any idea how I automate this with say Powershell or az clie or something else?
thanks
Russ
This question was answered by Microsoft:
Issue description:
You are unable to change the user name for the Office 365 API connection
Scope definition:
To provide assistance on the above issue with Office 365 API connection
Troubleshooting steps:
I tried the repro of the scenario and tried the below options
Used incognito window- did not help
Tried creating a new API connection with the new user- did not help
Logged out of the office 365 suite- did not help
Logged in to the machine with the new account- it worked
Resolution:
Based on the observations, I had discussions with the experts, and it seems the connector currently can only take windows AD authentication and hence the issue.
Product group has this feature update in the backlog and would be updating the connector in coming days, we do not have an ETA yet on this.
Workaround option:
Use portal from a server which doesn’t need domain user login. Login
to the server with non-domain user
Use Mozilla Firefox browser- this
has worked for few customers.