Graph-API | A standard Java library for Graphs

There are few cases where we cannot modify other user's data simply like that. Not just the permissions of API modify but also we need to be having a proper role to do some operation. As we are modifying the other user's password we should be having the highest or related role that can do it. I used to give Global Admin role which worked in my case.

As @Suresh suggested we can also use Authentication administrator role as it worked for him.

For permission to add to application may take few seconds time as it depends on different factors like internet etc.,

This is because in Kotlin you have to specify the variable as nullable if it will be null in any case.

The error is in this function

Apparently the issue was not in the code at all. I discovered that the 503 error was thrown only when a specific date's events were being read by the API. One of the events was rather large and I deleted it; after this the script works well.

This particular event has 16536 attendees listed, which I believe was the source of the error. Still unexplained is why the error was intermittent. I was eventually able to get graph explorer to successfully read the event, so perhaps the bug is in the Microsoft Graph SDK for PHP. I will post there to see if the devs want to capture this error condition.

Your api is wrong, try to change it to https://graph.microsoft.com/v1.0/me, see: update user api. If you use this api to modify user passwords, you must have the role of user administrator or global administrator.

If you want ordinary user roles to be able to change your own password, then you can use the /changePassword endpoint. I have answered similar questions before, and you can use it for your reference.

What @Joy said is absolutely correct. I have also tested this several times in Azure portal and MS graph api. I found a rule that all the old assignments not work, all the new assignments work fine. So, I also think it is a bug caused by the migration from App roles | Preview to App roles.

Currently, if you want to delete the old assignments, you can only delete the Enterprise Application and then create it again. (You delete the Enterprise Application will not delete the application in App registrations).

Refresh and create again:

Add:

It is a bug caused by the migration from App roles | Preview to App roles. This is an bug of Azure AD itself. I have reported the error message to Microsoft, and Microsoft should resolve it as soon as possible!

Microsoft uses oauth2 for all it's apis. An application is required to get a token, you can create a registration for free.

Just create your own application registration. This is the way forward.

Edit: previously suggested a way to circumvent the above statement. That is NOT recommended and no one should follow that suggestion

First problem, the 404 response, is likely due to the line breaks in the API URL, so remove those.

“Some of the aliases you requested do not exist” is due to the fact that user.uid is a the firebase-internal user id, not the Facebook user id. You can use the alias /me instead of an actual user ID, that will automatically resolve to the user (or page) the token belongs to.

If you are not getting the requested data fields, then you most likely did not add the user for the necessary permissions so far.

Neither of those methods will work for you. There is no SDK that can be used to do what you want.

There are (as far as I can tell) two undocumented command line switches "tel:" and "callto:".

Both will cause the current running instance of teams to prompt the user to call the thing in the uri.

You use "tel:" for e164 numbers. e.g. teams e164:+0015555551234

You use "callto:" for teams users. e.g. teams callto:user@company.com

If the id in ****** is your catalog id then your app must be missing permission. To access catalog, your app should have catalog_management and ads_management permissions. For better understanding you can refer this url. This document has example of real estate listings.