(HotFix)Enganga/move enable entraazureadalias to root module

[emmanuel-karanja]

Add Enable-EntraAzureADAlias to the RootModule .psm1 file for 'Microsoft.Entra'. Involved:

1. Removing 'Enable-EntraAzureADAlias' from individual sub-modules.
2. Adding Enable-EntraAzureADAlias to the 'Microsoft.Entra.psm1' file.
3. Inject RootModule section of the Microsoft.Entra.psd1 file.
4. Adding 'Enable-EntraAzureADAlias to the FunctionsToExport section of Microsoft.Entra.psd1.

[learn-build-service-prod]

Learn Build status updates of commit 4b0ecb5:

✅ Validation status: passed

File	Status	Preview URL	Details
build/Create-EntraModule.ps1	✅Succeeded
module/Entra/Microsoft.Entra/Applications/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Authentication/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Authentication/Revoke-EntraUserAllRefreshToken.ps1	✅Succeeded
module/Entra/Microsoft.Entra/DirectoryManagement/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Governance/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Groups/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Reports/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/SignIns/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Users/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Users/Get-EntraUser.ps1	✅Succeeded
src/EntraModuleBuilder.ps1	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit 8399248:

✅ Validation status: passed

File	Status	Preview URL	Details
build/Create-EntraModule.ps1	✅Succeeded
module/Entra/Microsoft.Entra/Applications/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Authentication/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Authentication/Revoke-EntraUserAllRefreshToken.ps1	✅Succeeded
module/Entra/Microsoft.Entra/DirectoryManagement/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Governance/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Groups/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Reports/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/SignIns/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Users/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Users/Get-EntraUser.ps1	✅Succeeded
src/EntraModuleBuilder.ps1	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[SamErde]

I have a design/philosophy question about this change: does moving this function to the Microsoft.Entra base module potentially break aspects of the modularized design?

Full Disclosure: My usage and testing has not focused at all on maintaining backwards compatibility with scripts that use the AzureAD module. However, consider this potential scenario:

An admin has the Microsoft.Entra.Authentication and Microsoft.Entra.Users sub-modules installed and can't/doesn't want to install any of the other modules for whatever reason. If they are still relying on aliases, would this break that functionality for them?

• It's definitely an edge case.
• It definitely still makes sense to consolidate general functions that aren't required directly for a sub-module's specific feature set.

Just thinking this through, and curious about your thoughts. Thanks!

[KenitoInc]

I have a design/philosophy question about this change: does moving this function to the Microsoft.Entra base module potentially break aspects of the modularized design?

Full Disclosure: My usage and testing has not focused at all on maintaining backwards compatibility with scripts that use the AzureAD module. However, consider this potential scenario:

An admin has the Microsoft.Entra.Authentication and Microsoft.Entra.Users sub-modules installed and can't/doesn't want to install any of the other modules for whatever reason. If they are still relying on aliases, would this break that functionality for them?

• It's definitely an edge case.
• It definitely still makes sense to consolidate general functions that aren't required directly for a sub-module's specific feature set.

Just thinking this through, and curious about your thoughts. Thanks!

Hey @SamErde
That was the original thinking we had when the consolidated aliases per sub-module. However the issue is since AzureAD was one module, customers migrating don't need to know which Entra Sub-module relates to the AzureAD function they are aliasing.

[SamErde]

Thanks, that makes sense!

[learn-build-service-prod]

Learn Build status updates of commit c76b4dc:

✅ Validation status: passed

File	Status	Preview URL	Details
build/Create-EntraModule.ps1	✅Succeeded
module/Entra/Microsoft.Entra/Applications/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Authentication/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/DirectoryManagement/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Governance/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Groups/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Reports/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/SignIns/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Users/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Users/Get-EntraUser.ps1	✅Succeeded
src/EntraModuleBuilder.ps1	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit fbee6ce:

✅ Validation status: passed

File	Status	Preview URL	Details
build/Create-EntraModule.ps1	✅Succeeded
module/Entra/Microsoft.Entra/Applications/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Authentication/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/DirectoryManagement/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Governance/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Groups/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Reports/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/SignIns/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Users/Enable-EntraAzureADAlias.ps1	✅Succeeded	n/a (file deleted or renamed)
module/Entra/Microsoft.Entra/Users/Get-EntraUser.ps1	✅Succeeded
src/EntraModuleBuilder.ps1	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel