BadRequest

[DarxonHU]

When running it from Azure DevOps pipeline I get the below "BadRequest" error:

WARNING: TenantId '***' contains more than one active subscription. First one will be selected for further use. To select another subscription, use Set-AzContext. WARNING: To override which subscription Connect-AzAccount selects by default, use Update-AzConfig
-DefaultSubscriptionForLogin 00000000-0000-0000-0000-000000000000. Go to https://go.microsoft.com/fwlink/?linkid=2200610 for more information. DEBUG: 11:08:28 AM - [ConfigManager] Got nothing from [DisplaySecretsWarning], Module = [], Cmdlet = []. Returning default value [True]. DEBUG: 11:08:28 AM - [ConfigManager] Got [On] from [LoginExperienceV2], Module = [], Cmdlet = []. DEBUG: 11:08:28 AM - [ConfigManager] Got nothing from [EnableLoginByWam], Module = [], Cmdlet = []. Returning default value [True]. DEBUG: 11:08:28 AM - [ConfigManager] Got nothing from [DisplayRegionIdentified], Module = [], Cmdlet = []. Returning default value [True]. DEBUG: 11:08:28 AM - [ConfigManager] Got nothing from [CheckForUpgrade], Module = [], Cmdlet = []. Returning default value [True]. DEBUG: AzureQoSEvent: Module: Az.Accounts:4.0.0; CommandName: Connect-AzAccount; PSVersion: 5.1.20348.2849; IsSuccess: True; Duration: 00:00:00.3659601; SanitizeDuration: 00:00:00.0000616 DEBUG: 11:08:28 AM - [ConfigManager] Got nothing from [EnableDataCollection], Module = [], Cmdlet = []. Returning default value [True]. DEBUG: 11:08:28 AM - ConnectAzureRmAccountCommand end processing. Extracting Subscriptions from Tenant *** DEBUG: 2025-01-17_11_08_28 - Checking report folder: C:\AzureResourceInventory\ Starting Resource Extraction.. DEBUG: 2025-01-17_11_08_28 - Starting Extractor function DEBUG: 2025-01-17_11_08_28 - Powershell Edition: Desktop DEBUG: 2025-01-17_11_08_28 - Powershell Version: 5.1.20348.2849 DEBUG: 2025-01-17_11_08_28 - Tags will be ignored DEBUG: 2025-01-17_11_08_28 - Number of Subscriptions Found: 44 DEBUG: 2025-01-17_11_08_28 - Invoking Inventory Loop for Resources DEBUG: 2025-01-17_11_08_50 - Invoking Inventory Loop for Network Resources DEBUG: 2025-01-17_11_08_50 - Invoking Inventory Loop for Backup Resources DEBUG: 2025-01-17_11_08_52 - Invoking Inventory Loop for AVD Resources DEBUG: 2025-01-17_11_08_53 - Invoking Inventory Loop for Resource Containers DEBUG: 2025-01-17_11_08_53 - Number of Resource Containers: 600 DEBUG: 2025-01-17_11_08_53 - Invoking Inventory Loop for Advisories DEBUG: 2025-01-17_11_09_01 - Number of Advisors: 5718 DEBUG: 2025-01-17_11_09_01 - Invoking Inventory Loop for Retirements ##[error]Operation returned an invalid status code 'BadRequest' ##[error]PowerShell exited with code '1'. Added TLS 1.2 in session.

As it can be seen, the ARI module got succesfully "invoked", it started to collect the data, but failed after "Invoking Inventory Loop for Retirements".
The Service Connection's App Registration has "Owner" permission over the Subscriptions.