> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/enterprise/admin-console/admin-console-16.6.md).

# Admin Console 16.6

Released on March 31, 2022

## Features

* **EM-5178:** Automated SSO Migration from On-Prem to Cloud

More information about the migration tool can be found here:

[SSO Migration to Cloud](/sso-connect-on-prem/jp/sso-migration-to-cloud.md)

The Admin Console allows the creation of SSO Connect and SSO Connect Cloud on same node on provisioning screen and will display the status of migration to cloud.

{% hint style="warning" %}
Please request a support engineer for assistance with migration before you start the process.
{% endhint %}

* **EM-5159: Redirect method for SSO login**

With this change, users who login to the Admin Console with SSO will login with a URL redirect (similar to the Web Vault) instead of a popup window. This change prevents timing-related issues with login.

## Bug Fixes

* **EM-5007:** Changing a user's name is not showing in search results
* **EM-5086:** Admin Console throws errors when approving SCIM users and teams.
* **EM-5222:** Show the authentication method used in ARAM login events.
* **EM-4895**: Users imported through CSV not being assigned to specified role


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/release-notes/jp/enterprise/admin-console/admin-console-16.6.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.