6.4.4

Changes (2024-Apr-17 / 6.4.4 Minor)

• fix issue #230
  • use AzAPICall PowerShell module version 1.2.1
• update API reference Microsoft.Security/pricings use API version 2024-01-01 (previous 2018-06-01)
• add 'Mutate' to ValidPolicyEffects
• location related tasks - use only physical locations (exclude logical)
• optimize collection of Role definitions that are used in Policy definitions

6.4.3

Changes (2024-Mar-19 / 6.4.3 Minor) - thanks @JanElholm

• Support for -DoAzureConsumptionPreviousMonth - Azure Consumption data should be collected/reported for the previous month

6.4.2

Changes (2024-Mar-14 / 6.4.2 Minor)

• optimize objects handling / best practices

6.4.1

Changes (2024-Mar-14 / 6.4.1 Minor)

• optimize objects handling / best practices

6.4.0

Changes (2024-Feb-06 / 6.4.0 Minor)

• change PowerShell parallel handling / batches
• add addition JSON outputs 'definitions_tracking' and 'assignments_tracking' (JSON filenames have no displayName included; GUIDs only)
• update ARM API-version for RBAC Role definitions. Using 2022-05-01-preview instead of 2018-11-01-preview consequently
• fix *_roleDefinitions.csv - description partially missing
• optimize array handling / best practices
• optimize getting private endpoint capable resource types / in case resource provider 'microsoft.network' is not registered, try with next available subscription instead of throwing
• use AzAPICall PowerShell module version 1.2.0
• documentation update - style guidance, links updates - kudos @ckittel

6.3.7

Changes (2024-Jan-08 / 6.3.7 Minor)

• fix: Ignore ARMLocation in case not Public Cloud (AzureCloud)

6.3.6

Changes (2023-Dec-17 / 6.3.6 Minor)

• fix: processing of Service Principal names that contain special characters
• fix: RBAC reporting correct RBAC Role assignment related Policy assignment Policy definition displayName
• update ARM API-version for CostManagement. Using 2023-03-01 instead of 2019-11-01

Changes (2023-Dec-15 / 6.3.5 Minor) - thanks @kaiaschulz

• Checking if the response of the storage account properties request is a byte array (type 'byte[]') and decode it to a string
• Different handling of BOM (Byte order mark) for XML returns on storage account properties request (since Powershell version 7.4.0)
• use AzAPICall PowerShell module version 1.1.85

6.3.4

Changes (2023-Nov-13 / 6.3.4 Minor)

• introduce new parameter -ARMLocation. Define the Azure Resource Manager (ARM) location to use (default is to use westeurope; this is used to optimize the built-in Azure RBAC Role definitions tracking)
• hardening the automated AzAPICall PowerShell module installation by adding retry mechanism in case of failure (Azure DevOps/GitHub)
• tolerating more up to date AzAPICall version when executing outside of Azure DevOps/GitHub
• update ARM API-version for Resources. Using 2023-07-01 instead of 2021-04-01
• update /.azuredevops/pipelines/AzGovViz.variables.yml
  • add parameter -ARMLocation
• update README.md
  • update API reference
• use AzAPICall PowerShell module version 1.1.84

6.3.3

Changes (2023-Oct-22 / 6.3.3 Minor)

• introduce new optional parameter -AzAPICallSkipAzContextSubscriptionValidation ref
• update ARM API-version for RBAC Role definitions. Using 2022-05-01-preview instead of 2018-11-01-preview. This will show us 'conditions' example
• update /.azuredevops/pipelines/AzGovViz.variables.yml
  • add parameter -AzAPICallSkipAzContextSubscriptionValidation
  • structure AzAPICall related variables
  • Azure Active Directory becomes Microsoft Entra ID
• update README.md and setup.md
  • OIDC for Azure DevOps
  • update API reference
  • Azure Active Directory becomes Microsoft Entra ID
• use AzAPICall PowerShell module version 1.1.83

6.3.2

Changes (2023-Sep-12 / 6.3.2 Minor)

• another fix for AzAPICall issue43. Use-case scenario will be documented in the near future. Kudos to Asbjørn Nielsen (fellowmind dk) @AsbjornNielsen
• use AzAPICall PowerShell module version 1.1.79