Applications

Application registrations define how third-party services and internal tools connect to your environment. Losing one can break integrations that business operations depend on.

What Kasca backs up

Kasca captures a full snapshot of your application registrations, including their properties at the time of backup — not just the object itself, but the registration details and configuration properties that make it functional.

What happens when something goes wrong

Accidental deletions happen more often than most teams expect. A bulk operation targeting the wrong scope, a script with a missing filter, a junior admin with too much access — any of these can result in objects being removed that took significant time and effort to configure.

Microsoft provides a 30-day soft-delete window during which objects can be easily restored through the platform itself. The problem arises when that window has passed. Once an object is hard-deleted, native recovery is no longer possible.

This is where Kasca comes in. Using your backup data, Kasca can rehydrate hard-deleted application registrations back into your environment — something Microsoft cannot do on its own. Secrets and certificates cannot be restored (by design — they are never stored), so those will need to be regenerated. However, the backup retains all other available data from the original object — including descriptions, validity periods, and configuration details — so you are not rebuilding from memory.

Restoring with Kasca

Restoration is granular — you can restore an individual application without touching anything else. For objects still within Microsoft's soft-delete window, Kasca uses the soft-deleted object. For everything else, Kasca's rehydration gives you a path back that would otherwise not exist.