msgraph-sdk-powershell VS microsoft-graph-docs

Information here https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/1439 indicates problems with specific powershell and module versions. My testing has not found a working combination.

You can go to the GitHub for the PowerShell SDK and write in for specific help with the MSGraph cmdlets, over the course of a few days/weeks usually, but a lot of times it ends up as something like "That isn't available in the Graph API, so we can't do anything with it" Example 1 Example 2 Example 3

Hey man, just wanted to follow up with you on this. So it turns out the query isn't as straight forward as doing a select-object clause. When you listed that "identities" is the possible key term, I switched up my Google tactic and instead searched for get-mguser identities.emailAddress and I found this github comment thread.

MSOL is quickly being depreciated. The Licensing endpoints were already turned off this month. If you're building anything new at this point, you should be using Graph.

I have seen this post on Github that I don't understand completely. Maybe I have to wait for Microsoft to correct it ? Do you also have the same problem ? Thank you for your help !

That's cool to make your own cmdlets and all, but Microsoft.Graph.DeviceManagement latest version was published 12 days ago. You may want to double check the Graph SDK. https://github.com/microsoftgraph/msgraph-sdk-powershell/wiki/MS-Graph-PowerShell-Modules

I don't think you are alone. Looks like Ms have not bothered/want to push conditional access/Forgot about it.

Created Github issue: https://github.com/microsoftgraph/microsoft-graph-docs/issues/18095

See https://github.com/microsoftgraph/microsoft-graph-docs/blob/main/concepts/auth-v2-user.md

For example, a recent commit added this BitLocker example:

You could write a script to iterate through all of the UserMailbox recipients looking at the Default user's AccessRights to the calendar folder and any time you find one set to None set it back to AvailabilityOnly. Or if you don't want to mess around with trying to connect to Exchange Online PS via a scheduled task you could use the MS Graph API calendarPermission to do the same thing. It won't stop people trying to change it but at least it'll automate setting it back.

If you want to dig deep, you can use the method that @Absoblogginlutely posted under here: (GitHub Page)[[https://github.com/microsoftgraph/microsoft-graph-docs/issues/7010] But fair warning - you would have to somehow get the Teams auth header every hour or so when it expires.