i want fetch last access date of tfs user using rest api - tfs

I have seen there is rest api for getting the data but that api using api version "4.1-preview.1" as its is supporting tfs 2018, however my tfs version is this
"Version 16.122.27102.1" so that api version is not supporting me.so i could not able to fetch the "UserEntitlements details" using api.
api : https://abc.visualstudio.com/_apis/userentitlements?api-version=4.1-preview.1
How would I manage to get the similiar data as tfs 2018 ??

User Entitlements API is for VSTS only, it is not applicable to TFS.

Related

Migrate existing users (and tokens) from Outlook REST API to MS Graph

Hi we have a system that already has a large userbase (100k+) of microsoft users which we push updates to, using the refresh token we have saved during their inital signup.
The REST APi will get deprecated on the 30th of November in favour of the Graph API. https://devblogs.microsoft.com/microsoft365dev/outlook-rest-api-v2-0-deprecation-notice
I have upgraded all API calls to the new graph api but am faced with the following error:
CompactToken parsing failed with error code: 8004920A
From further digging it seems like it is caused since the tokens are not interchangable between the two APIs:
https://learn.microsoft.com/en-us/answers/questions/1010061/migration-from-rest-to-graph-refreshed-token-throw.html
So is there a way to port these users into the new API without having them to go through the oauth flow again, since we don't have a functionality to request this from the users?
We were calling the token flow without the scope parameter, which was working fine with the DEPRECATED API. But with the new Graph API, we had to add the relevant scope query param, and the returned token worked with the new API calls. Hope this helps someone.
Also related, the Exchange Team has published on Nov 23, 2022 that the decommissioning has been pushed to 2023, and that they will give a 6 month notice prior to the actual decommission date.
https://techcommunity.microsoft.com/t5/exchange-team-blog/outlook-rest-api-v2-0-and-beta-deprecation-update/ba-p/3682745

How to register an attendee for a webinar via Microsoft Graph API

I want to register attendee in Microsoft Team Webinar by using my system, for this I need an API.
Does Graph API support to add an attendee for a webinar?
Using following graph API you can set the allowedRegistrant as everyone or organization.
1.Create meetingRegistration - POST /me/onlineMeetings/{id}/registration
2.Update meetingRegistration - PATCH /me/onlineMeetings/{id}/registration
These APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported.
Ref Doc:
https://learn.microsoft.com/en-us/graph/api/meetingregistration-post?view=graph-rest-beta&tabs=http
https://learn.microsoft.com/en-us/graph/api/meetingregistration-update?view=graph-rest-beta&tabs=http

Getting "MailboxNotEnabledForRESTAPI" While trying to use MS Graph APIs

We have used MS Graph API(MSAL) in one SAP Ui5 Application and have implemented Mail api, Calender api and MailboxSetting apis so far. It was working fine till Nov 2020 (Last checked in Nov 30 2020).
Suddenly this application keeps throwing the error "{"error":{"code":"MailboxNotEnabledForRESTAPI","message":"REST API is not yet supported for this mailbox."}}".
Though we have not changed a single code or any changes has been done in Azure portal or in the envirmental set up.We do have a Hybrid envirment mailbox set up.
The strange thing is the same APIs are working in MS Graph Explorer but not from our custom Apps. But when we use the token generated by Graph Explorer, APIs works from our custom apps also.
We compared the both tokens using jwt.ms. Scopes and other attributes are the same. Only 'wids' attribute is not present in our custom App's Token(We are using Implicit Grant flow).
which flow do MS Graph Explorer use, so it works there ?(If Authorization
flow is the issue).
Is it that only Graph Explorer is allowed to make API calls to On-Premise
Mailbox and the custom applicationa are not?
Is there any other factor, we should consider to solve this ?
Thank You,
Arpita
This error happens when trying to access a mailbox that is not hosted in EXO. Check where your target mailbox is hosted and use auto discover to locate the right endpoint for that environment.

Microsoft Office 365 Apps Usage

I am trying to collate information corresponding to Microsoft 365 Apps Usage of our employees as shown in some reports on Admin Portal(admin.microsoft.com). We are facing some challenges in getting report data corresponding to these in our code.
I need following information for integration in our web application:
Do we have any Graph API or PowerShell cmdlet(not deprecated) exposed which can be integrated in our code to get Microsoft Apps Usage Data(like ProPlusUsageUserDetail excel data downloaded from admin portal)?
Can we get Version Details of Microsoft 365 Apps and Services being used by users?
We have already used graph api GetOffice365ActiveUserDetail (adding link below for reference) which give usage for only Microsoft Services and not Apps:
https://learn.microsoft.com/en-us/graph/api/reportroot-getoffice365activeuserdetail?view=graph-rest-1.0
We need same kind of information for Microsoft 365 Apps (Word, Excel, PowerPoint etc.)as well .
You can try portal.office.com and check the reports to see if you have related report is available apart from that, at this point i am not aware such information you can request from Microsoft Graph APIs. Consider raising a feature request in User voice, so that Microsoft can consider it. Here's the link for it https://microsoftgraph.uservoice.com/forums/920506-microsoft-graph-feature-requests?query=report

Can I create channels in Microsoft Teams using the API?

I am not a programmer - just trying to find the answer to a question about Microsoft Teams. I'd like my dev team to automate some processes in Teams including the creation and archive of channels. Can anyone let me know if this is possible via the API?
TIA
Channels are available in Microsoft Graph API (on beta endpoint). To create a channel, you can POST to a /channel endpoint:
POST https://graph.microsoft.com/beta/teams/{id}/channels
Content-type: application/json
{
"displayName": "Channel Name",
"description": "Channel Description"
}
{id} in the request URL is the ID of the Team (not to be confused with the ID of Group that owns the team). The request needs to contain Auth token (bearer token) in Authorization header.
More info about this method is available on Microsoft Graph documentation page:
https://learn.microsoft.com/en-us/graph/api/channel-post?view=graph-rest-1.0
I've created a command line tool that lets you bulk create new Microsoft Teams channels using the Graph APIs outlined above. It's written in C# and .NET Core, and includes instructions that describe how you register your application for use with your Teams environment.
https://github.com/tamhinsf/ChannelSurf
Feel free to use it as an example or starter kit for your own needs!
Sorry, this capability is not exposed through a developer API right now but is on the roadmap.

Resources