Skip to main content

January 2021

Flexera One introduced the following new features and enhancements this month.

Cloud Cost Optimization​

Cloud Cost Optimization added the following new feature in January 2021.

Support for multiple Google Cloud billing accounts in the same Flexera Org​

note

This feature is available with Cloud Cost Optimization.

Additional support around Google Cloud Platform (GCP) accounts are now added in the Flexera Cloud Cost Optimization platform.

Google Cloud Platform allows customers to enable BigQuery billing export for multiple billing accounts. In addition, Google can issue new billing accounts when changes occur to how customers are billed.

In the Flexera Cloud Cost Optimization platform, population of the Bill Source dimension has now changed, as follows:

Changed FromChanged To
google-<projectID>gcp-<billingAccountID>-<unique-32-characters>

The following provides an example of this change:

Changed FromChanged To
google-myProjgcp-012345-678901-ABCDEF-abc123def456abc123def456abc123de

This allows for on-boarding billing data from multiple Google Cloud Platform billing accounts into the same Flexera organization, even when the actual billing datasets are in the same Google project.

To achieve this within Flexera One, navigate to Administration > Cloud Settings > Settings, and then on the Billing Configuration tab click the ADD A CLOUD BILL button.

For more information on Google Cloud Billing, refer to the Google cloud billing documentation.

SaaS Management​

SaaS Management added the following enhancements in January 2021.

Office 365 Client Credentials license differentiation and license reclamation​

note

This enhancement is available with SaaS Management.

License differentiation​

Flexera One offers a license differentiation feature that allows you to view users by license type. To view this license differentiation feature, navigate to the Activity tab of the Office 365 Client Credentials Application Details screen where you can filter and export the Office 365 Client Credentials license types.

The total spend for the Office 365 Client Credentials accounts displayed in the Office 365 Client Credentials Application Details screen is based on the license cost details entered in the License Details tab. For details, refer to Entering license details for license differentiation.

Application Task Tracking

License Differentiation has been added to Office 365 Client Credentials in the Application Task Tracking chart.

License reclamation​

License reclamation is the process of taking back licenses from application users. These users fall into one of the following scenarios.

  • Employees who are inactive in your organization’s HR Roster
  • Application users who have never logged in to an application
  • Application users who are inactive

Reclaimed licenses help optimize SaaS spend and increase procurement efficiency because you avoid buying additional licenses for new license requests. You also limit security risks by reclaiming licenses from inactive employees in your HR Roster. To achieve these goals, Flexera One provides an automated license reclamation workflow. In addition, Flexera One’s reclamation history tracks each step of the license reclamation workflow and each license reclamation status. For details, refer to Reclaiming Licenses.

The Office 365 Client Credentials integration instructions were updated to reference the following license reclamation information:

Office 365 Client Credentials license reclamation​

As part of the Reclamation task, only the license that is tracked under the Office 365 Client Credentials application is reclaimed or unassigned. The remaining licenses that are assigned to the user are unaffected. To reclaim an Office 365 Client Credentials license, see Reclaiming Office 365 User Licenses.

Minimum Permissions Required​

User.ReadWrite.All permissions are required to modify the license assigned to the user.

Reclamation API endpoint​

https://graph.microsoft.com/v1.0/users \{id | userPrincipalName\}/assignLicense

Application Task Tracking​

Reclamation has been added to Office 365 Client Credentials in the Application Task Tracking chart.

Office 365 license reclamation​

note

This enhancement is available with SaaS Management.

License Reclamation is the process of taking back licenses from application users. These users fall into one of the following scenarios.

  • Employees who are inactive in your organization’s HR Roster
  • Application users who have never logged in to an application
  • Application users who are inactive

Reclaimed licenses help optimize SaaS spend and increase procurement efficiency because you avoid buying additional licenses for new license requests. You also limit security risks by reclaiming licenses from inactive employees in your HR Roster. To achieve these goals, Flexera One provides an automated License Reclamation workflow. In addition, Flexera One’s reclamation history tracks each step of the License Reclamation workflow and each License Reclamation status. For details, refer to Reclaiming Licenses.

The Office 365 integration instructions were updated to reference the following license reclamation information:

Office 365 License Reclamation​

As part of the Reclamation task, only the license that is tracked under the Office 365 application is reclaimed or unassigned. The remaining licenses that are assigned to the user are unaffected. To reclaim an Office 365 license, see Reclaiming Office 365 User Licenses.

Minimum Permissions Required​

User.ReadWrite.All permissions are required to modify the license assigned to the user.

Reclamation API endpoint​

https://graph.microsoft.com/v1.0/users \{id | userPrincipalName\}/assignLicense

Application Task Tracking​

Reclamation has been added to Office 365 in the Application Task Tracking chart.

Updated Zoom integration instructions​

note

This enhancement is available with SaaS Management.

The table of stored information for the Application Roster and Application Access integration tasks was updated and an API endpoint was added to the Zoom Integration Instructions.

Application Roster​

The User ID is now stored in Flexera One.

Application Access​

The Meeting Name and Meeting Date are now stored in Flexera One.

Application Access API endpoint​

The following API endpoint is now available.

https://api.zoom.us/v2/users/<userId>/meetings