Microsoft.Graph.Files Doesn't work in Azure Automation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reproducing the issue in an Azure Automation PowerShell 7.4 runtime with Microsoft.Graph.Files 2.38.1, using the supplied runbook and Get-Command -Module Microsoft.Graph.Files check. Compare the runtime result with interactive module behavior and investigate why the module's cmdlets are not discovered. Done means the Files cmdlets, including Get-MgDriveItemContent, are found in the runtime.
Written by the indexing model from the issue text.
Description
Describe the bug
This is the same as the closed bug in https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/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_- Dominant language
- C#
- Stars
- 898
- Forks
- 230
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 31
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-sdk-powershell
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
status:waiting-for-triage type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in microsoftgraph/msgraph-sdk-powershell
Similar issues
-
untriaged
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/dotnet-api-docs#13095 ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
newrelic/newrelic-dotnet-agent#3850 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
LuckyPennySoftware/AutoMapper#4660 ·