🪲[Bug]: RequiredModule is not installed

[hjorslev]

Describe the bug

https://github.com/hjorslev/IntuneOperator/actions/runs/22925515792

The above workflow fails on MacOS, probably because the module Microsoft.Graph.Authentication is not loaded (though it works fine on Linux/Windows).

In order to resolve this I have attempted to add a required module to https://github.com/hjorslev/IntuneOperator/blob/initial/src/manifest.psd1. However, when the module is build the required module is not present in the module manifest.

Version information

PSModule/Process-PSModule/.github/workflows/workflow.yml@60bdf8a5a4c92c53fcf2a8d23f7d5f5c93e6864e # v5.4.3

To reproduce

I have updated the manifest in src/manifest.psd1 and attempted to populated the RequireModules section.

Code snippet

@{
 Author = 'Frederik Hjorslev Nylander'
 Copyright = '(c) 2026 Frederik Hjorslev Nylander. All rights reserved.'
 Description = 'A PowerShell module for managing and enhancing Microsoft Intune.'
 PowerShellVersion = '7.4'
 RequiredModules = @(
 @{ ModuleName = 'Microsoft.Graph.Authentication'; ModuleVersion = '2.28.0' }
 )
}

I would expect that the above RequiredModules section would be present in the builded version of manifest, however, it is not:

@{
 RootModule = 'IntuneOperator.psm1'
 ModuleVersion = '999.0.0'
 CompatiblePSEditions = @(
 'Core'
 'Desktop'
 )
 GUID = '51ea3dd6-6e01-423a-ad25-101f46f0580f'
 Author = 'Frederik Hjorslev Nylander'
 CompanyName = 'hjorslev'
 Copyright = '(c) 2026 Frederik Hjorslev Nylander. All rights reserved.'
 Description = 'A PowerShell module for managing and enhancing Microsoft Intune.'
 PowerShellVersion = '5.1'
 ProcessorArchitecture = 'None'
 TypesToProcess = @()
 FormatsToProcess = @()
 FunctionsToExport = @(
 'Get-IntuneDeviceLogin'
 )
 CmdletsToExport = @()
 VariablesToExport = @()
 AliasesToExport = @()
 ModuleList = @()
 FileList = @(
 'IntuneOperator.psm1'
 'README.md'
 )
 PrivateData = @{
 PSData = @{
 Tags = @(
 'Linux'
 'MacOS'
 'PSEdition_Core'
 'PSEdition_Desktop'
 'Windows'
 )
 LicenseUri = 'https://github.com/hjorslev/IntuneOperator/blob/main/LICENSE'
 ProjectUri = 'https://github.com/hjorslev/IntuneOperator'
 IconUri = 'https://raw.githubusercontent.com/hjorslev/IntuneOperator/main/icon/icon.png'
 }
 }
}

Relevant output

As the manifest is not updated with the RequiredModules the Import-Module job does not find any module:

VERBOSE: - Manifest file path: [outputs/module/IntuneOperator/IntuneOperator.psd1]
Resolving dependencies
 Resolving dependencies
 - Reading [outputs/module/IntuneOperator/IntuneOperator.psd1]
 - Found [0] module(s) to install
 - Resolving dependencies - Done
Importing module
 VERBOSE: Loading module from path '/Users/runner/.local/share/powershell/Modules/IntuneOperator/999.0.0/IntuneOperator.psd1'.
 VERBOSE: Loading module from path '/Users/runner/.local/share/powershell/Modules/IntuneOperator/999.0.0/IntuneOperator.psm1'.
 VERBOSE: Importing function 'Get-IntuneDeviceLogin'.
WARNING: /Users/runner/.local/share/powershell/Modules/IntuneOperator/999.0.0

[hjorslev]

Of course, this could also be a matter of me not understanding something. Anyways, thanks for a fantastic workflow. It really helps speeding up building stuff.

[MariusStorhaug]

Hi Frederik Hjorslev (@hjorslev), thank you! I will fix some docs on this, but the idea is to add the requirements using the #Requires way of defining requirements, and the process will "compile" this and gather all the reqs and add them into the manifest file. Todo: Add docs for defining requirements.

[MariusStorhaug]

Frederik Hjorslev (@hjorslev) Please let me know here if that actually fixed the issue. :)
If not, would you want all of this to be handled better some other way? My thought on this design decision is that when you are writing functions, you want to know what parts of the code actually takes a dependency on something instead of just having that tracked in the "static" manifest file.

[hjorslev]

Hi Marius Storhaug (@MariusStorhaug)

It works!

However, I went with the solution of adding it to the initializer.ps1. That might a case of shooting sparrows with cannons...

I think that adding it to the cmdlets itself makes even more sense. Because in a years time I will completely have forgotten what cmdlets will require authentication. While writing this, I just updated my project to reflect this and it works flawlessly. Required module are now added directly to the cmdlet instead of the initializer.ps1. So this is definitely the way to go I think.

So it was "just" the missing docs 😊

[MariusStorhaug]

Frederik Hjorslev (@hjorslev) Great to hear. Will add some docs on that now. Thank you for the issue and glad to hear it works for you!