Closed stvnmbr1 closed 1 year ago
These issues are not related. There is an issue within the MSTeams PowerShell Module and the authentication method for applications is not available for this Teams Resource.
This is the reason for this issue> https://github.com/microsoft/Microsoft365DSC/issues/3394#issuecomment-1604587054
Closing and moving discussions to #3394
Description of the issue
Suddenly the pipelines stopped working after updating version and m365dscdependencies.
I found out that https://github.com/microsoft/Microsoft365DSC/commit/73aa87145896e0dd183b3cc72185d98fe4552560 actually deletes these parameters in set/get/test functions. Can this be the cause?
https://github.com/microsoft/Microsoft365DSC/commit/73aa87145896e0dd183b3cc72185d98fe4552560#diff-0b2d6a2ece5c19d2123b9bd3377e4ebb5f927aa56f17dfbb036b24504856c4aa
reverting the version of Microsoft365DSC module does not fix the issue. I'm currently in progress reverting the dependencies to [Release 1.23.719.1], which seems to have caused the issue but i am still investigating.
Microsoft 365 DSC Version
1.23.809.1
Which workloads are affected
Azure Active Directory, Exchange Online, Office 365 Admin, OneDrive for Business, Planner, Power Platform, Security & Compliance Center, SharePoint Online, Teams, other
The DSC configuration
No response
Verbose logs showing the problem
Environment Information + PowerShell Version