authentication issues

[ed-rosario-arpa-h]

Prerequisites

• This issue has an informative and human-readable title.

ScubaGear Version

I am unable to authenticate to my Tenant when running scuba. During the initialization process Microsoft.Graph.Authentication 2.26.1 updated to version 2.27.0. When I Invoke-SCuBA the log below shows that Microsoft.Graph.Authentication 2.26 is not found. How to pin the modules versions during the initialization step? How can I force scuba to install and use Microsoft.Graph.Authentication v2.26?

WARNING: Error running Get-MgBetaIdentityConditionalAccessPolicy: Could not load file or assembly 'Microsoft.Graph.Authentication, Version=2.26.1.0, Culture=neutral, PublicKeyToken=REDACTED' or one of its dependencies. The system cannot find the file specified.

Operating System

Windows 11

PowerShell Version

5.1

M365 Environment and License(s)

M365 Environment: gcc
Don't know the lic type

🐛 Summary

At C:\Program Files\WindowsPowerShell\Modules\ScubaGear\1.5.0\Modules\Orchestrator.psm1:1371 char:13

•         throw $InvokeReportErrorMessage
  

•         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

• CategoryInfo : OperationStopped: (Fatal Error inv...o file>: line 1:String) [], RuntimeException
• FullyQualifiedErrorId : Fatal Error involving the Report Creation.

Ending ScubaGear execution. Error: Invalid JSON primitive:

Steps to reproduce

failed scubareport.txt

Expected behavior

My report to be created

Output from Initialize-SCuBA (optional)

No response

[j-rat]

@ed-rosario-arpa-h see the issue I posted about earlier today. It may help you out.

#1674

[ed-rosario-arpa-h]

I can try this fix, however how do I prevent this from happening in the future? I run my reports automatically pulling scuba from PS gallery. How can force the application to use a specific version of a module?

[schrolla]

@ed-rosario-arpa-h This was a temporary issue due to the dependent modules needing to all be at the same version. Microsoft has since (over the weekend) released the remaining Graph modules. The easier solution now should be to re-run Initialize-SCuBA so that all the Microsoft.Graph.* modules update to 2.27.0 and then re-run ScubaGear.
If that fails, the workaround in #1674 is also an option.
We have some updates that will reduce dependencies on these modules in the future that will be included in an upcoming ScubaGear release that should alleviate some of these issues. However, you can prevent this by manually installing specific versions of dependent modules rather than running Initialize-ScubaGear to "pin" to specific versions. Over time, however, this could also lead to breakage and additional maintenance as dependencies change over time.