Authorization_IdentityNotFound Error in Microsoft Contoso Airlines Team Example - microsoft-graph-api

I am getting an Authorization_IdentityNotFound error when I try to run the Microsoft Contoso Airlines Team Example.
I registered my App at apps.dev.microsoft.com, added in all the Graph permissions (as well as Admin Consent) and added the Web.config.secrets file as described in the ReadMe.
Do I have to do something with an authentication token? I am using an Office 365 Developer Account.
Here are my permissions:
I am able to log in when running the app in Visual Studio, and I am able to get to the screen where you can select the airlines and crew members, but the error pops up when I click on 'Create Team'.
Here is the error:

Related

Azure DevOps Server 2019/2020 Access Levels Page Not Found

I am running Azure DevOps Server 2019 cu7. When I click on the Access Levels link at the Project Collection level, I get a page not found error for ../_admin/_licenses. I then upgraded my development farm to ADO Server 2020, and still have the same issue.
The app pool accounts are both System and I have added the System account to the iis_iusrs group.
Also, i get a page not found error when trying to hit the/_api/licenses/export api to try to get around the page not found error when using a browser.
It seems that you do not have the permission Edit Instance-level information
Steps:
Open Azure DevOps Server Administration Console->click the option Application Tier->click the button Administer Security->select [Team Foundation]\Team Foundation Valid Users and ensure the permission Edit instance-level information is set the allow. Then we could check the Access Levels page.
Result:
The permission is set to Deny
The permission is set to Allow

Azure AD B2C Application won't show up as an option to add role assignment. (Graph API)

I'm following this documentation:
https://learn.microsoft.com/en-us/azure/active-directory-b2c/microsoft-graph-get-started?tabs=app-reg-ga
And I found another question answered that I thought fit my case:
https://learn.microsoft.com/en-us/answers/questions/199433/can39t-add-role-assignments-to-azure-b2c-applicati.html
My problem is that the app that I registered will not appear as an option when I try to follow the "Enable user delete and password update" portion of the documentation.
I am also mindful of the notice "Please allow a few minutes to for the permissions to fully propagate." But I've at it for 2 hours now, so I don't think that is the problem.
Here is my App and its API permissions:
And my B2C Tenant:
Microsoft has answered this question on this thread as follows:
Hi All · Thank you for reaching out.
There seems to be an issue with the UI. I will report the issue to the product team and get it addressed.
However, as of now, you can follow below steps and use PowerShell to add application to the User Administrator role:
Install latest Azure AD PowerShell Module.
Run Connect-AzureAD -TenantId Your_B2CTenant.onmicrosoft.com and sign in with Global Administrator account in that tenant.
Run Get-AzureADDirectoryRole cmd and copy the object id of the User Administrator role.
Navigate to Azure AD > Enterprise Applications > Search the app and copy the object id of the app.
Run Add-AzureADDirectoryRoleMember -ObjectId object_ID_copied_in_Step3 -RefObjectId object_ID_copied_in_Step4 cmdlet.
To verify, navigate to Azure AD B2C > Roles and Administrators > User Administrator. You should see the application present under this role

TFS ServiceEndpoint Issue

I'm having troubles trying to add Azure Resource Manager Service Endpoint in TFS 2017. When i enter the required data and click on "Verify Connection" I can see the verified
when I click OK button , I get the following error
Does anyone have any idea how to fix it?
First double check if you have followed below tutorials to create this service Endpoint:
How to Setup an Azure Resource Manager Endpoint
Creating an Azure Resource Manager Service Endpoint
Such as make sure you have gave the service principal access to create resources in your subscription.
Click Browse and select Subscriptions
Select the subscription you are using
Click the Access button
Click Add
Select Contributor as the roll
Search and select the name of the application you just created
Click OK to grant the service principal access to your subscription
For more troubleshooting, please take a look at this link-- How to: Troubleshoot Azure Resource Manager service endpoints
Update from OP
Issue fixed by Upgrade to TFS2017 update1.

Office 365 GatewayTimeout error / the preferred replica is unavailable

I'm attempting to run the Office 365 Starter Project for ASP.NET MVC and following the readme here...
https://github.com/OfficeDev/O365-ASPNETMVC-Start/blob/master/README.md
I'm click the "Register your app" link in the add connected service dialog. I sign in and see the message "Registering the directory application..." Then after about a minute, I get the error message "Office 365 GatewayTimeout".
After a search turned up nothing, I restarted Visual Studio as admin and after the same process got the error "the preferred replica is unavailable"
Has anyone come across/resolved this error?
I was able to resolve this by moving the directory to my drive root. It turns out that some names in this particular project were too long for Visual Studio.

Unable to create new Team Project - TF30170 and TF249061

We recently ungraded and moved TFS from 2013 update 4 to TFS 2015 Update 1. When trying to create a new Team Project we keep getting the error below. Any help would be greatly appreciated.
Error
TF30170: The plugin Microsoft.ProjectCreationWizard.Reporting failed
during task Populate Reports from group Reporting.
Explanation
Plugin error text: “TF249061: You cannot access the
following report item: /Tfs2010OlapReportDS. Access was denied because
your account does not have one or more permissions required to access
this item.”
User Action
Contact your Team Foundation Server administrator.
The issue turned out to be that the current service account had access to all the data sets except for Tfs2010OlapReportDS. To grant access to that I had to log into the report manager and grant access to service account using the old service account that was used on the previous installation of TFS.

Resources