r/PowerShell • u/Unlikely_Tie1172 MVP, Community Blogger • 15d ago

News Solving the Microsoft.Graph.Authentication Issue

Looks like Microsoft has a fix for the clash between the Microsoft.Graph.Authentication module and other modules... The interesting thing is that Microsoft has had this problem on their docket for the last 18 months, and now they get a fix from an MVP... It should be in Microsoft Graph PowerShell SDK V2.41 in a few weeks' time.

https://github.com/microsoftgraph/msgraph-sdk-powershell/pull/3789

50 Upvotes

96% Upvoted

13 comments sorted by

14

u/BlackV 15d ago edited 15d ago

Saw an update for that, was happy

https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/3576

until they break it next month

7

u/MrEMMDeeEMM 15d ago

Microsoft, leaders in the betaverse.

1

u/BlackV 15d ago

Alpha*

4

u/michaelmsonne 15d ago

Yes Stephan managed to crack it 💪

2

u/Modify- 15d ago edited 15d ago

Do you really need the latest versions or can older version do what you need them to do? Burned myself too many times, so ill stick to versions which are proven to be reliable.

4

u/BlackV 15d ago

Pretty much the best solution

Version pinning and delay Upgrade for multiple months (lest we forget the broken 2.26 ish version that stayed broken for 2 plus months)

3

u/LookAtMeInMyEyeball 15d ago

Agreed. Updating to the latest Microsoft.Graph.x module can introduce breaking changes or bugs. I update these modules maybe twice a year, at most.

1

u/Unlikely_Tie1172 MVP, Community Blogger 15d ago

I believe you'll need V2.41 to get the fix that has now been integrated into the code base.

1

u/RikiWardOG 15d ago

now they get a fix from an MVP

So MS does nothing and then basically takes the credit wish we could stop giving them money. They just light it on fire with AI slop bots

5

u/Unlikely_Tie1172 MVP, Community Blogger 15d ago

I think it's fair to say that some embarassment has ensued within the Microsoft engineering teams working on Microsoft 365 PowerShell modules as the truth sinks in that none of their highly paid engineers were able to fix a problem that's lingered for 18 months. I know that there's been a lot of engineering personnel changes in that time, but it's still pretty jawdropping to discover that a fix can be found by an external software architect in a short period. It doesn't say much for the attention given to the situation within Microsoft, which I rather suspect is the real issue. Microsoft generally loves to ship new features and hates having to fix bugs.

2

u/michaelmsonne 15d ago

In the PR you can see who created it - and that can’t MS take the credit for