Optimization Automation Feature Catalogue

Optimization Automation

Zluri is building an Optimization Automation module which allows you to periodically review and take action on underutilized licenses automatically without any manual intervention.


The below images depict how this feature is expected to work.


You can navigate to the optimization tab under applications.


It gives you a summary of total optimizable licenses ( Sum of undeprovisioned, unused, underused licenses), Estimated wastage of last month, Potential savings, & Relalized savings for the application.




Configurations

The optimizable licenses are identified based on the configuration that you choose to have in the settings tab. To detect unused licenses, you can select to have the configuration at 30/60/90 days since last use and to detect underused licenses. You can select to have configuration at 30/40/50 percent of usage.


You can also select which licenses and which accounts are to be optimized for which bucket. For example, you might not want to revoke a free license if it is not being used. However, you would want to revoke a free license if the user has left the organization.



Zluri will identify the unused & underused licenses based on these configurations and populate them in the dashboard.


You can also select an offboarding playbook for each of the 3 buckets. And pick with what frequency the playbook has to run to remove/downgrade the licenses of the users.


Slack Notification

A Slack notification to the admins can also be configured, which will send the list of optimizable licenses to the admin.


Playbooks & Actions:

A playbook is a set of actions that can be run on a single/set of users.

Automated Actions: 

With directly integrated applications, you can perform the actions directly in the application through APIs.


Manual Tasks

Manual tasks are a workaround where no direct integration is available between the Zluri and the application or the application does not have relevant APIs. Here a mail/slack notification is triggered to the assignee of the task, and they can mark the task as completed. This task will also be available in the task dashboard.,



Custom HTTP Request:

A custom HTTP request can also be sent to an API and Webhook.




Jira Actions:

The task can be assigned to someone through Jira, and once the task is marked as completed, it will show up in Zluri.



Request to forego

You can also ask users whether they want to keep a license or let go of a license and, based on that, take action. The user receives a notification on Slack, and they can choose if they want to keep or forego a license. You can configure other actions based on the user’s response to the message. You will be able to see the user’s response on the platform.


Can’t find what you are looking for? Let us help you!

Optimization Automation Feature Catalogue

Modified on Fri, 27 Oct 2023 at 01:24 AM

Optimization Automation

Zluri is building an Optimization Automation module which allows you to periodically review and take action on underutilized licenses automatically without any manual intervention.


The below images depict how this feature is expected to work.


You can navigate to the optimization tab under applications.


It gives you a summary of total optimizable licenses ( Sum of undeprovisioned, unused, underused licenses), Estimated wastage of last month, Potential savings, & Relalized savings for the application.




Configurations

The optimizable licenses are identified based on the configuration that you choose to have in the settings tab. To detect unused licenses, you can select to have the configuration at 30/60/90 days since last use and to detect underused licenses. You can select to have configuration at 30/40/50 percent of usage.


You can also select which licenses and which accounts are to be optimized for which bucket. For example, you might not want to revoke a free license if it is not being used. However, you would want to revoke a free license if the user has left the organization.



Zluri will identify the unused & underused licenses based on these configurations and populate them in the dashboard.


You can also select an offboarding playbook for each of the 3 buckets. And pick with what frequency the playbook has to run to remove/downgrade the licenses of the users.


Slack Notification

A Slack notification to the admins can also be configured, which will send the list of optimizable licenses to the admin.


Playbooks & Actions:

A playbook is a set of actions that can be run on a single/set of users.

Automated Actions: 

With directly integrated applications, you can perform the actions directly in the application through APIs.


Manual Tasks

Manual tasks are a workaround where no direct integration is available between the Zluri and the application or the application does not have relevant APIs. Here a mail/slack notification is triggered to the assignee of the task, and they can mark the task as completed. This task will also be available in the task dashboard.,



Custom HTTP Request:

A custom HTTP request can also be sent to an API and Webhook.




Jira Actions:

The task can be assigned to someone through Jira, and once the task is marked as completed, it will show up in Zluri.



Request to forego

You can also ask users whether they want to keep a license or let go of a license and, based on that, take action. The user receives a notification on Slack, and they can choose if they want to keep or forego a license. You can configure other actions based on the user’s response to the message. You will be able to see the user’s response on the platform.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article