Describe the bug
This is the same as the closed bug in #2756
load the Microsoft.Graph.Files module into a runtime environment and attempt to use it. All attempts fail because cmdlets like Get-MgDriveItemContent cannot be found.
Expected behavior
The cmdlets should be found.
How to reproduce
Make sure that the runtime environment includes Microsoft.Graph.Files
Create a runbook to connect to the Graph with a managed identity (or any other way you like)
Run this code:
$FilesCmdlets = Get-Command -Module Microsoft.Graph.Files
If ($FilesCmdlets) {
Write-Output "Here's what I found for Files cmdlets"
$FilesCmdlets | Format-Table Name, Version
Write-Output ("{0} cmdlets found" -f $FilesCmdlets.count)
}
No cmdlets are found, but there are 1,252 in the module (the result when reported interactively). I guess some resource issue is being met.
SDK Version
2.38.1
Latest version known to work for scenario above?
The previous reports of the bug go back to 2.19
Known Workarounds
Only workaround is to use the Graph API requests
Debug output
Click to expand log
```
</details>
### Configuration
Azure Automation
PowerShell 7.4 runtime environment
Microsoft.Graph.Files 2.38.1 module
### Other information
_No response_
Describe the bug
This is the same as the closed bug in #2756
load the Microsoft.Graph.Files module into a runtime environment and attempt to use it. All attempts fail because cmdlets like Get-MgDriveItemContent cannot be found.
Expected behavior
The cmdlets should be found.
How to reproduce
Make sure that the runtime environment includes Microsoft.Graph.Files
Create a runbook to connect to the Graph with a managed identity (or any other way you like)
Run this code:
$FilesCmdlets = Get-Command -Module Microsoft.Graph.Files
If ($FilesCmdlets) {
Write-Output "Here's what I found for Files cmdlets"
$FilesCmdlets | Format-Table Name, Version
Write-Output ("{0} cmdlets found" -f $FilesCmdlets.count)
}
No cmdlets are found, but there are 1,252 in the module (the result when reported interactively). I guess some resource issue is being met.
SDK Version
2.38.1
Latest version known to work for scenario above?
The previous reports of the bug go back to 2.19
Known Workarounds
Only workaround is to use the Graph API requests
Debug output
Click to expand log
```