Azure Automation Account adding Microsoft.Graph module failed

Question

Azure Automation Account adding Microsoft.Graph module failed

cthivierge 3,976

Hi,

we are deploying Azure Automation Account using Azure pipelines and it work well. But when we try to add Microsoft.Graph module using ARM templates, it fail every time with the following error.

Error importing the module Microsoft.Graph. Import failed with the following error: Orchestrator.Shared.AsyncModuleImport.ModuleImportException: While importing the module, an error occurred while processing the module content. Internal error message: Function Update-MgShareListContentTypeColumnLink cannot be created because function capacity 4096 has been exceeded for this scope.. at Orchestrator.Activities.SetModuleVersion.ExecuteInternal(CodeActivityContext context, String moduleName, ModuleLanguage moduleLanguage, String pythonModuleVersion, String modulePath, Guid accountId, Guid moduleVersionId, Int64 moduleContentByteSize, String storageUri, Int32 moduleVersion) at Orchestrator.Activities.SetModuleVersion.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

I have tried using Azure hosted VM as well as our self hosted VM's but it fail with the same error.

I did another test and instead of importing the Microsoft.Graph module using a ARM template, i used a inline script

New-AzAutomationModule -name Microsoft.Graph -AutomationAccountName $AutAccount.Name -ResourceGroupName $(resourceGroupName) -ContentLink https://www.powershellgallery.com/api/v2/package/Microsoft.Graph/1.11.0

But it still fail with the same error message.

Any help will be appreciated

Ryan Hill 16,621 Reputation points Microsoft Employee

2022-08-15T19:20:53.397+00:00

@cthivierge I figured you were using 1.11.0 from your inline script. In piecing out the error, I can't speak with certainty, but it seems to me that a list in your template is too large. Can you share a snippet of your template that your automation account is using that includes a list? Just for clarity, has your template always worked or is this a new template you haven't been able to get working?
cthivierge 3,976 Reputation points

2022-08-15T19:43:52.047+00:00

Hi,

Here is a part of our json for the automation account modules... i have 39 modules in that json.

I import the Microsoft.,Graph module from another json file

Ryan Hill 16,621 Reputation points Microsoft Employee

2022-08-15T19:20:53.397+00:00

@cthivierge I figured you were using 1.11.0 from your inline script. In piecing out the error, I can't speak with certainty, but it seems to me that a list in your template is too large. Can you share a snippet of your template that your automation account is using that includes a list? Just for clarity, has your template always worked or is this a new template you haven't been able to get working?
cthivierge 3,976 Reputation points

2022-08-15T19:43:52.047+00:00

Hi,

Here is a part of our json for the automation account modules... i have 39 modules in that json.

I import the Microsoft.,Graph module from another json file

Answer 1

Ryan Hill 16,621 Microsoft Employee

@cthivierge came across https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/1449. Appears this is a PowerShell 5.1 limitation but there are some proposed workarounds.

Use PowerShell 7+
Only load the Microsoft.Graph modules you template needs
Set $maximumfunctioncount to its max value of 32768.

Let me know down below either way if all, any, or none of the workarounds worked.

---
EDIT 2022 September 14 These are the only workarounds that are available. Microsoft.Graph has ~7k unique API paths which is why you're hitting that error. All the commands simply can't fit into PowerShell 5.1. For Automation Accounts, change the runtime to 7+.

cthivierge 3,976 Reputation points

2022-08-15T19:55:51.507+00:00

Hi,

I tried to deploy all Microsoft,Graph modules using a simple Powershell command like this one...

New-AzAutomationModule -name Microsoft.Graph.Compliance -AutomationAccountName $AutAccount.Name -ResourceGroupName $resourceGroupName -ContentLink https://www.powershellgallery.com/api/v2/package/Microsoft.Graph.Compliance/1.11.0

It's not working for the versions 1.11.0 and 1.10.0 but work well for version 1.9.6...

The pipeline is running with the version 1.9.6... i should know if it's working or not within the next hour.

I will try using the $maximumfunctioncount to 32768 but i already did using a value of 8192 as well as 10000 but both failed.

But... why it's working with a lower version ? it should not affect the deployment ?

Thanks
cthivierge 3,976 Reputation points

2022-08-15T22:14:48.773+00:00

The pipeline finished without any error.

So i can deploy all microsoft.graph modules using powershell or azure pipeline up to version 1.9.6.

Version 1.10.0 and 1.11.0 are failing with the same error.

I will try later by adding the $maximumfunctioncount = 32768 to see if it's working or not.

Thanks
Ryan Hill 16,621 Reputation points Microsoft Employee

2022-08-16T02:54:33.847+00:00

Please do let me know. I'll ask to see what's why 1.9.6 works but >1.10.0 fails but that could be a module error. I'll add our discussion to the aforementioned GitHub issue.
Morten Lerudjordet 6 Reputation points

2022-09-01T10:24:00.257+00:00

Seems like you cant change $maximumfunctioncount in AA for the module repository.
I even tried running the module import as a 7.1 Runbook but still it will show the same limit of 4096.

So seems like this needs to be a change by the AA team as the module environment is likely different than the environment the Runbooks are running in.

Could have used everything in 7.1, but Az-module still does not support importing 7.1 modules yet. Can only do it through the portal and that is too tedious.
Lucas LEVEAU 1 Reputation point

2022-09-15T06:27:20.467+00:00

Hello @Ryan Hill , thank you for your update, before trying PowerShell 7+, I have two questions :
Since all my PowerShell runbooks in my automation account run in PowerShell 5.1 and with Microsoft.Graph, what happen if I update Microsoft.Graph with PowerShell 7+ ? Will they stop working ?
And will I need to update each graph modules in PowerShell 7+ for better compatibility ?

Answer 2

I just did a test using Powershell to update all Microsft.Graph modules.
All of them work well from 1.9.6 to 1.11.0 except for "Microsoft.Graph". It fail with the same error:

Error importing the module Microsoft.Graph. Import failed with the following error: Orchestrator.Shared.AsyncModuleImport.ModuleImportException: While importing the module, an error occurred while processing the module content. Internal error message: Function Update-MgShareListContentTypeColumnLink cannot be created because function capacity 4096 has been exceeded for this scope.. at Orchestrator.Activities.SetModuleVersion.ExecuteInternal(CodeActivityContext context, String moduleName, ModuleLanguage moduleLanguage, String pythonModuleVersion, String modulePath, Guid accountId, Guid moduleVersionId, Int64 moduleContentByteSize, String storageUri, Int32 moduleVersion) at Orchestrator.Activities.SetModuleVersion.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

and i have added the $maximumfunctioncount = 32768 at the beginning of the Script.

There should be something that has changed from module version 1.10.0+...

thanks

Lucas LEVEAU 1 Reputation point

2022-08-26T09:15:12.953+00:00

Hello, do you guys have any news on this topic ?
I'm facing the same issue

For the workarounds:

Using Powershell 7+ => You need to update all modules in the right order in the Azure Portal, you can't do it with New-AzAutomationModule and it would take too long to do it manually on 150+ modules

Only load the Microsoft.Graph modules you template needs => I only installed the dependancies of Microsoft.Graph

$maximumfunctioncount = 32768 => Not working or I am the using in the right way
cthivierge 3,976 Reputation points

2022-08-26T10:36:25.17+00:00

From what i have tested, only Microsoft.Graph modules from verson 1.10 and higher have this issues.

We decided to rollback versions to 1.9.6 and it's working well.
Ryan Hill 16,621 Reputation points Microsoft Employee

2022-09-15T02:49:20.96+00:00

@cthivierge @Lucas LEVEAU please see my edited response above.

Answer 3

Morten Lerudjordet 6

I wrote 2 runbooks to handle module management for AA. It also does dependencies.

Can either find them under Runbooks and Browse gallery or:
https://github.com/mortenlerudjordet/Update-PSGalleryModulesInAA
https://github.com/mortenlerudjordet/Import-PSGalleryModulesToAA

Azure Automation Account adding Microsoft.Graph module failed

3 answers

Activity