Axiad Cloud March 2023 Release Notes

Last Updated: September 21, 2023

New Features

"Single Pane of Glass" to Azure

Axiad Cloud now has the ability to track all authentication methods issued in Azure and report on them within the Unified Portal. This includes primary authenticators such as Windows Hello for Business, Microsoft Authenticator, and FIDO2, as well recovery authenticators like Temporary Password Access or SMS OTP. 

This equips your IT department with a more complete picture of the current state of your passwordless rollout across your environment. If authorized, Help Desk Operators have the option to delete any of those credentials.

New Report Columns

You can now display the first name, last name, and UPN when looking at or reporting on users.

Automatic Action Grouping

If two or more actions are available to a user or operator on a given device, the first two actions display as buttons. Additional actions are then grouped in the context menu. 

Any time-sensitive actions such as Renew are always listed first.

Selective Certificate Lifecycle Management

Help Desk Operators are now able to selectively suspend/resume/revoke a certificate on a given device without affecting other credentials on the same device. This is useful for cases where for instance ownership of a specific encryption certificate is tied to a distinct background check.

Enhancements

SCIM Enhancements

SCIM 2020 PATCH format

Previously, the Axiad Cloud/Azure AD integration only supported SAML SSO. We now support SCIM 2020 PATCH format, which simplifies the SCIM configuration when connecting your Axiad Cloud instance to an Azure tenant. 

SCIM Imports (MyCircle Users/Groups)

MyCircle rules can now refer to entities and attributes that were imported from a SCIM-compliant provider, such as Azure AD, Ping Federate, or Okta.

Bug Fixes

Unified Portal

• Workflow certificate configuration changes now save as expected when you click the Save button. (PM-2798)
• The Emergency section no longer displays if there is nothing to show, and/or if the user doesn't have the .userResetSecurity permission. (PM-823)
• The issue where some mobile OTP authenticators displayed as OTP Device has been resolved. (PM-1452)