Features at a Glance

Supported Azure Services


Manage blob storage (containers & blobs), file storage (shares & files), queue storage (queues & messages), table storage (tables & entities) in your accounts. Also perform basic management operations on the accounts.

Cosmos DB

Manage database, containers, stored procedures, triggers, user defined functions and data in your accounts targeting SQL, Gremlin and Table API. Also perform basic management operations on the accounts.

Redis Cache

Manage databases, and keys in your Redis Cache accounts through a user interface or in-built console. Also perform basic management operations on the accounts.

Service Bus

Manage queues, topics, subscriptions and messages in your Service Bus accounts. Also perform basic management operations on the accounts.

Cognitive Search

Manage indexes, data sources, indexers, synonyms and data in your Cognitive Search accounts. Also perform basic management operations on the accounts.

Cloud Service

You can explore Classic Cloud Services running in your Azure Subscription and perform basic management operations on them.


Connect to your Azure Subscriptions using Work/Personal account and perform basic management operations on the supported resources. Also launch Cloud Shell and Portal from inside the application.

Other Features


Cerulean enables you to add certain kind of resources as favorites (in other words bookmark those resources) so that you can conveniently access these resources directly instead of navigating through the resource hierarchy.
Some features related to favorites in Cerulean are:
  • Ability to group favorite resources in folders/sub-folders.
  • Ability to assign friendly name to a favorite resource.
  • Ability to open a favorite resource in "read-only" or "read-write" mode to prevent accidental deletes and updates.
  • Following resource types can be added as favorites:
    • Storage: Blob containers, file shares, queues, and tables.
    • Cosmos DB: SQL API containers, Gremlin API containers, and Table API tables.
    • Cognitive Search: Cognitive search indexes.
    • Redis Cache: Redis cache databases.
    • Service Bus: Service bus queues and subscriptions.



Cerulean is highly customizable. Almost every aspect of the application can be customized according to your preferences.
Some examples of customization features available in Cerulean are:
  • Ability to view date/time in local or UTC.
  • Ability to customize upload/download behavior like upload block size, compression/decompression settings.
  • Ability to view Redis Cache keys in hierarchical format.


Resource Category

Cerulean has this unique feature wherein you can assign a "category" e.g. "Dev", "QA" or "Prod" to a resource so resources can be grouped together based on their category for easier management of those resources.
You can view the resources based on:
  • Resource Type (Default): Resources are grouped based on type e.g. all storage accounts will be grouped under "Storage Accounts" type.
  • Resource Category: Resources are grouped based on category e.g. all resources under "Dev" category will be grouped together.
  • Resource Category & Type: Resources are grouped based on category and then type.
  • No Grouping: Resources are not grouped and are presented as is.

Group By Type

Group By Category

Group By Category & Type

No Grouping

Friendly Name

When we create resources in Azure, we have to follow certain naming convention (e.g. all lower case letters, max 25 characters, no spaces etc.). Furthermore sometimes Azure automatically assigns some random names to the resources. All of these make it less user friendly.
Cerulean has a unique feature where you can assign a friendly name to a resource and then the application displays that friendly name inside the application making it easier for you to manage the application.
For example, we have a storage account named "cerebrata3310" that stores the diagnostics logs for one of our Virtual Machines. We have given that account a friendly name of "Cerebrata VM Logs".

Friendly Name


To prevent accidental deletes and updates, Cerulean has a distinct feature of setting permissions on a resource. These permissions are specific to Cerulean only and opens up a resource with specified permissions.
Currently following permissions can be set on a resource:
  • Read Only: Resources are opened in read-only mode and no updates or delete operations can be performed on the resource.
  • Read Write: Resources are opened in read-write mode and only read and update operations can be performed on the resource. Delete operations are blocked.
  • Full (Default): Resources are opened in read-write-delete mode and all operations can be performed on the resource.



This is another unique feature of Cerulean where long running operations like blob uploads, downloads etc. are executed via an out-of-process background tasks so that the impact on the UI from these tasks will be minimal.
Cerulean can keep these tasks running even after it has terminated so that you don't have to keep the application running only because these long running operations are executing.
You can monitor the progress of these tasks, view detailed logs collected by these tasks, cancel tasks or even resubmit the tasks if they fail (and are retryable).