Cloud Settings: Billing Configuration and Custom Tags We are pleased to announce the Cloud Cost Billing Configuration and Custom Tags pages have each been given their own individual pages under the Administration > Cloud Settings. Administration > Cloud Settings > Billing Configuration Administration > Cloud Settings > Custom Tags This added benefit now means that you can favorite each page individually for ease of use. These cloud settings are further explained in the following product documentation links: Custom Cost Dimensions Adding a Cloud Bill in the Billing Configuration User Interface ... View more

Bill Processing Status The Bill Processing Status dashboard allows you to view the status of your bill connects. The Flexera One Org Owner role is required to view this dashboard. This dashboard can be found by navigating to the Administration menu and selecting Bill Processing Status from the Cloud Settings submenu. The Bill Processing Status dashboard allows you to view: Bill Account Credentials Bill Status Import History Click the toggle at the upper-left corner to view everything on this page or errors only. Credentials The Credentials column displays the validity of your credentials. If an Invalid credential error badge appears, click the link to update the account’s credentials under Administration > Cloud Settings > Billing Configuration. This feature is available for all cloud vendors. Bill Status The Bill Status column displays actionable Common Bill Ingestion (CBI) errors. If an error badge appears, click the link which opens a slideout. This error slideout includes a data table with the: Error Message Detected (time frame) Status Source ID Click the paper icon at the end of each table row to quickly copy the error information. Import History Clicking the View link in the Import History column opens an Import History slideout. In this slideout, you can view the import history for each of your bills from the last three months. The Import History feature is available for all cloud vendors except for AWS connections that are not enabled for Common Bill Ingestion (CBI). For further details, refer to the Product Documentation Link For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

New Okta OAuth2 Integration The new Okta OAuth2 platform, a single Sign-On (SSO) provider, offers cloud software that helps companies manage and secure user authentication into modern applications. These are the differences between Okta Platform and Okta OAuth2: Integration of Okta OAuth2 with SaaS Management Instructions for obtaining a Client Id and a Private Key Application Permissions New User Role for a Super Administrator Credentials required include a Private Key API Endpoints have a different syntax See also: The Okta OAuth2 integration instructions listing has been added to the Application Task Tracking chart. The Okta OAuth2 integration instructions listing has been added under Single Sign-On in the Instructions listing. For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

Azure Client Credentials Workaround to Grant the Directory.Read.All Permission In the Azure Active Directory page   Request API permissions, the option   Azure Active Directory Graph API   is no longer available as it will be deprecated next year. As a workaround to grant the "Directory.Read.All" permission: From the Request API permissions page, select the tab: APIs my organization uses. Search and select   Windows Azure Active Directory. For further details, see the Obtaining Client Credentials and Tenant ID section of the Azure Client Credentials integration instructions. For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

Initial Ingestion of SaaS Activity Data When a new integration is created within Flexera One, typically 30 days’ worth of historical SaaS activity data is retrieved from the application. Exceptions to the initial 30-day period are noted within the individual integration instructions. Activity data is tracked for active, inactive, and never active users. For a description of these terms, see Common User Activity Terms Found in SaaS Management Help. The following scenarios describe the SaaS activity data that is available for each time period: SaaS activity data immediately available after initial integration SaaS activity data after 30 days SaaS activity data beyond the activity threshold SaaS activity data immediately available after initial integration You will immediately see the following SaaS activity data in the Flexera One UI: Users that have logged in within the last 30 days appear as Active. Users that have not logged in within the last 30 days appear as Never Active. Inactive users appear as 0. SaaS activity data after 30 days After 30 days, 60 days of SaaS activity data appears in the Flexera One UI, as explained in the formula below. first 30 days + 30 elapsed days = 60 days of data After 30 days, you will see the following SaaS activity data in the Flexera One UI with 60 days as the selected activity threshold: Users that have logged in within the last 60 days appear as Active. Users that have not logged in within the last 60 days appear as Never Active. Inactive users appear as 0. SaaS activity data beyond the activity threshold Users that have not logged in since the selected activity threshold appear as Inactive in the SaaS Management UI. Example: 60 days is the selected activity threshold Users that have logged in 61 days ago but not since, appear as Inactive in the Flexera One UI.   For more details, see the Product Documentation: Initial Ingestion of SaaS Activity Data For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

From the Dashboards menu, click SaaS to open the SaaS Dashboard. The SaaS Dashboard enables you to see at a glance how much you are spending on Software as a Service (SaaS). The SaaS Dashboard also provides insight into how application licenses are used across organizations, so organizations can right-size application licenses to optimize spend. The SaaS Dashboard was redesigned to present data in a more consistent and consumable way, and the dashboard data is updated more frequently. For more details, refer to: How often is the SaaS Dashboard updated? SaaS Dashboard Data Descriptions and Sources How often is the SaaS Dashboard updated? Previously, the entire SaaS Dashboard data set was updated once a day beginning at 7:00 UTC. Now the SaaS Dashboard data is updated when Flexera One pulls in new information regarding active/inactive/never active user counts. The new user counts cause the dashboard counts to be recalculated. Once the dashboard counts are recalculated, the data updates are displayed in the SaaS Dashboard. Some examples of pulling in new active/inactive/never active user count information include: The application’s Application Roster integration task is executed. New usage events are pulled in. An application’s activity threshold is modified. Licenses are added or modified in the application’s Licenses tab. SaaS Dashboard Data Descriptions and Sources The following table provides SaaS Dashboard data descriptions and sources. SaaS Dashboard Data Description Flexera One Data Source Total Annual Spend This is the sum of annual spend from all managed applications. Managed SaaS Applications Managed Applications This is the number of applications your organization is managing using Flexera One. NOTE: The Managed Applications count excludes inactive applications. Managed SaaS Applications Managed Licenses This is the total number of all managed licenses. NOTE: If an application has multiple license types (see Activity Tab) listed in Flexera One (Example: Office 365 Plan E3 and Plan E5), each license type counts as one managed license. All SaaS Licenses Underutilized Accounts This number is the sum of all inactive and never active accounts across all managed applications. Underutilized SaaS Accounts Application Usage This graph displays usage data for the top 5 applications with the highest annual spend. Application usage is displayed with the number of active, inactive, and never active users. Clicking the application name or a bar in the Application Usage graph takes you to the application’s Overview Tab. SaaS License Usage Spend by Department This graph displays the top 12 departments with the highest annual spend. The total SaaS application spend is broken down by department or location, based on your organization’s HR Roster, with a cumulative departmental SaaS spend across all applications. All SaaS Users Upcoming Renewals This graph displays the following upcoming renewal information for managed applications: License end date Annual license spend. For applications with licenses that span over an 18-month, two-year, or three-year period, the annual spend is prorated. All SaaS Licenses   Product Documentation Link: SaaS Dashboard For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

Office 365 and Office 365 Client Credentials Blocked Users SaaS Management’s Office 365 and Office 365 Client Credentials integrations reflect “Blocked” users in Microsoft, along with the previously shown “Active” users. For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

Logout Redirect URL for Identity Providers When you log in to Flexera One through your organization's identity provider, you will be directed to a logout redirect URL when your session ends. A Flexera One session may end when you log out or when your session expires due to inactivity. If no logout redirect URL is set, you will be directed to the Flexera One login page when your session ends. One suggested use for this feature is to set the logout redirect URL to the homepage of your organization's identity provider. An https:// URL is strongly recommended. However, an http:// URL is also valid). NOTE: When the logout redirect URL is changed, it only affects newly created sessions after the update. Any session already active during the update will not be affected by the update. To observe the changed behavior, log out of Flexera One, then log in to Flexera One again through the identity provider and when that session ends, the new logout redirect value will be active. For further details, refer to Setting Up an Identity Provider in Flexera One for: Azure AD Okta External Identity Provider For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

AppExchange (Salesforce) Direct Integration with SaaS Management AppExchange (Salesforce) is an online marketplace where Salesforce customers can add third-party SaaS applications to their Salesforce instances. See the AppExchange (Salesforce) website for a list of available applications. Flexera One’s SaaS Management now offers a direct integration with AppExchange (Salesforce) to manage the usage of Salesforce’s third-party SaaS applications. Benefits of integrating AppExchange (Salesforce) with SaaS Management Third-party SaaS applications are managed in AppExchange (Salesforce) using managed packages. Currently, Salesforce customers do not have visibility into the usage of all managed packages across Salesforce instances. Optimizing managed packages in Salesforce requires a cumbersome manual process. Using SaaS Management’s direct integration with AppExchange (Salesforce), you can view your managed packages for all your Salesforce instances in one place. SaaS Management identifies users who are no longer with your company and are still assigned managed package licenses — enabling you to repurpose or reclaim these licenses to save time and money. For more information, refer to the AppExchange (Salesforce) integration instructions. For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

Flexera One Login Page UI Refresh We’ve given the Flexera One login interface a refresh, and we think you’ll like it. The Flexera One Login Page UI Refresh will be available to all customers in early September. Alongside a brand new visual design, the following updates have occurred on the Flexera One login page for your ease of use. Customers can view the latest report from Flexera One. Password validation as you type helps users resolve errors easily. Tabs to navigate between username / password and SSO sign in are replaced with a toggle button for clearer separation and ease of use. Now you can use SSO through button instead of the tab. "Remember my discovery hint" helps the user to recollect their memory. The whole page is accessible and mobile-friendly. Questions? Please speak with your Customer Success Manager, and we'll be glad to help. Documentation: Logging into Flexera One or Resetting your Password ... View more

The latest release of Flexera One's SaaS Management capability now provides the ability to see all Salesforce licenses for all orgs rolled up into one view. The new Salesforce Overview enables you to drill down to a particular Salesforce instance to view licenses, view user activity, and reclaim user licenses. Watch the three-minute Flexera One SaaS Management Video. For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more

Viewing Inventory Normalization Statistics Inventory Normalization Statistics provide insights as to how hardware and software inventory has been normalized. These statistics can be found in Flexera One by navigating to the Data Collection menu. From the IT Visibility Inventory Status submenu, click Inventory Normalization Statistics. These statistics are described in the tables below for hardware and software. For the online help reference, see Viewing Inventory Normalization Statistics. Hardware Normalization Statistics Statistic Description Per discovery source Evidence count is the count of evidence (that is, the information collected from a system to detect the existence of the hardware) from each discovery source being ingested in the normalization process. Total evidence count This statistic is broken down by evidence type: Consolidated evidence indicates the evidence that is retained as a result of merging, consolidation or deduplication process amongst multiple evidence, which are used to recognize the exact same hardware.   Duplicate evidence indicates the evidence that is not retained as a result of merging, consolidation or deduplication process because it is considered as a duplicate amongst multiple evidence, which are used to recognize the exact same hardware. Consolidated inventory count This statistic is broken down by recognition status: Recognized to model indicates that, out-of-the-box, the evidence is fully recognized (that is, associated with a Technopedia catalog entry) all the way to the hardware model level.   Recognized to product indicates that, out-of-the-box, the evidence is only partially recognized to the hardware product level.   Recognized to manufacturer indicates that, out-of-the-box, the evidence is only partially recognized to the manufacturer level.   Unrecognized indicates that, out-of-the-box, the evidence is not recognized by the normalization process. Therefore, the evidence will go through the gap-fill process. Inventory count This statistic is broken down for reach recognition status by: Active is the count of hardware that is managed and taken into consideration when calculating the final inventory count for further downstream use-cases (such as license consumption calculation).   Ignored is the count of hardware that is not taken into consideration when calculating the final inventory count for various reasons (for example, the hardware is being retired, disposed of, etc.).   Software Normalization Statistics Statistic Description Per discovery source Evidence count is the count of evidence (that is, the information collected from a system to detect the existence of the software) from each discovery source being ingested in the normalization process. Total evidence count This statistic is broken down by evidence type: Installer evidence indicates the evidence collected from a local (device-based) list of installed software, such as Add/Remove Programs or MSI.  NOTE: The installer evidence count currently doesn’t include Operating System Evidence.   File evidence indicates evidence in the form of a file that is found on a computer—it may simply be the name of the file, or the information found within the file (such as with ISO-compliant software identification [SWID] tags).  NOTE: File evidence is not currently available in Flexera One.   Other evidence indicates evidence other than installer or file evidence.  NOTE: Other evidence is not currently available in Flexera One. Installer Evidence count This statistic is broken down by recognition status: Recognized indicates that, out-of-the-box, the evidence is recognized (that is, associated with a Technopedia catalog entry) to either the software release level or the software product level.   Unrecognized indicates that, out-of-the-box, the evidence is not recognized by the normalization process. Therefore, the evidence will go through the gap-fill process. Recognized evidence count This statistic is broken down for reach recognition status by: Consolidated evidence indicates that the evidence is retained as a result of merging, consolidation or deduplication process amongst multiple evidence, which are used to recognize the exact same software.   Duplicate evidence indicates that the evidence is not retained as a result of merging, consolidation or deduplication process because it is considered as a duplicate amongst multiple evidence, which are used to recognize the exact same software.   Irrelevant evidence indicates that the evidence has been recognized as not having any value to the customer (for example, it’s a device firmware, a driver, a miscellaneous application add-on, plugin or other negligible files, etc.). Therefore, the evidence is separated out from the calculation of the software install count. Consolidated evidence This statistic identifies software that is installed in the inventory and is broken down by: Active is the count of software that is detected on an active hardware. Therefore this evidence is taken into consideration for further downstream use-cases (such as license consumption calculations).   Ignored is the count of software that is detected on an ignored hardware.   For more information on new features and enhancements for Flexera One, see  What's New in Flexera One . ... View more