CloudCheckr Product announcements and release notes logo
Back to Homepage

Product announcements and release notes

Hint: Subscribe at the top to stay notified when new releases are published!

Subscribe to Updates

Labels

  • All Posts
  • Fix
  • Announcement
  • release notes
  • Improvement

Jump to Month

  • April 2025
  • February 2025
  • December 2024
  • November 2024
  • October 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • July 2022
  • April 2022
  • February 2022
  • January 2022
  • December 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
release notes
a year ago

November 27th, 2023 - Release Notes 33.1

Azure Subscription Family API

We have added new functionality to allow the creation, modification, and deletion of Azure Subscription Families APIs – see below for specifics regarding each API call: 

  • Create: API Reference Guide 
  • Modify: API Reference Guide 
  • Delete: API Reference Guide 

Bug Fixes

  • Addressed an issue where the payer closes a month as expected, and the payee was not being notified
  • Addressed an issue where the high precision cost export was not being respected in some CSV exports
  • Fixed an issue where – in certain scenarios – if autoscaling were used, the EC2 instance report was omitting some EC2 instances that should have been included 
  • Resolved an edge case where the untagged resource report was incorrectly flagging a resource that had been tagged properly  
  • Resolved an issue where tag values wouldn’t be visible in a MAV dashboard pane if multiple payers were selected
  • Fixed an edge case where L2s were not receiving friendly names correctly