Table of Contents
- Overview
- Introduction
- Understanding the "Is Active" and "Suspended" Attributes in Veza
- Google Cloud's Licensing Model for Suspended Accounts
- Implications for Veza Queries and Reporting
- Additional Information
Overview
This guide explains why Veza marks suspended Google Cloud users as Is Active = TRUE and how this relates to Google's licensing model. It also provides best practices for managing suspended accounts in Veza to avoid billing inaccuracies and overcharges.
Introduction
Google Cloud's licensing model charges for suspended accounts as if they are active, which can lead to confusion when these statuses are reflected in Veza. This article explores the reasoning behind this behaviour.
Understanding the "Is Active" and "Suspended" Attributes in Veza
In Veza, the attribute Is Active = TRUE is used to indicate that a user is still considered part of the organisation’s active licensing pool, regardless of their suspension status in Google Cloud. This reflects Google's policy of charging for suspended accounts as if they are active.
Google Cloud's Licensing Model for Suspended Accounts
Google Cloud charges for licenses based on the total number of users, including those marked as suspended. Suspended users retain access to certain resources (e.g., existing projects), which keeps them within the billing scope. As a result, Veza mirrors this by maintaining Is Active = TRUE even when Suspended = TRUE.
Implications for Veza Queries and Reporting
When querying dormant users in Veza, ensure your filters account for both Is
Active = TRUE and Suspended = TRUE.
This prevents overlooking suspended users who are still incurring charges. Suspensions do not reduce licensing costs unless the user is deleted entirely.
Due to reasoning mentioned previously in this article, suspended users appear active in reports.
Additional Information
For more details on managing suspended accounts, refer to Google's documentation.
Comments
0 comments
Article is closed for comments.