---
title: "How to Deploy VirtoSoftware Apps in Your Own Azure Tenant"
description: "Run VirtoSoftware Apps entirely inside your own Azure subscription and M365 tenant. Full data sovereignty, OAuth/OIDC auth, and a step-by-step setup guide."
url: https://www.virtosoftware.com/news/deploy-virtosoftware-in-own-azure-tenant/
language: en-US
last_modified: 2026-09-28T00:00:00+02:00
translations:
  de: https://www.virtosoftware.com/de/news/deploy-virtosoftware-in-own-azure-tenant/index.md
---

# How to Deploy VirtoSoftware Apps in Your Own Azure Tenant

 [by Sergi Sinyugin](https://www.virtosoftware.com/author/svirtosoftware-com/) Published: Jun 8, 2026 Latest update: Sep 28, 2026

Reading Time: 2 mins

[News](https://www.virtosoftware.com/news/)

For a growing number of enterprises, the first question about any new app isn’t “what does it do?” — it’s “where does our data live?” With tighter regulations and rising security expectations, that question deserves a clear answer.

So here’s ours: you can run the [**Virto Calendar App**](https://www.virtosoftware.com/deploy-virto-apps-in-m365/), [**Virto Alerts**](https://www.virtosoftware.com/microsoft-365/virto-alerts-and-reminders-app/) and (soon) [**Virto Kanban**](https://www.virtosoftware.com/microsoft-365/virto-kanban-board-app/) [**entirely inside your own Azure subscription and Microsoft 365 tenant**](https://www.virtosoftware.com/deploy-virto-apps-in-m365/). No third-party servers, no external dependencies, no data leaving your environment.

We explained the *why* behind this model — data sovereignty, control, and transparency — in [When Security Comes First: Deploy VirtoSoftware Apps in Your Own Microsoft 365 Environment](https://www.virtosoftware.com/news/deploy-virto-in-your-m365-environment/). This post is the short version, plus a pointer to the full step-by-step instructions.

## What “in your own tenant” actually means

When you self-host Virto Calendar:

-   **Your App Service** hosts the application.
-   **Your Azure Table Storage** holds the data — in your region, under your retention and backup policies.
-   **Your Azure AD (Entra ID) app registration** governs authentication.

Authentication uses the standard Microsoft OAuth 2.0 / OpenID Connect flow, and all data is accessed under each signed-in user’s credentials via delegated Microsoft Graph permissions. In practice: users only ever see what they’re already authorized to see, and nothing crosses your security perimeter.

It’s the deployment model that makes the most sense for organizations in regulated industries — legal, government, finance, healthcare — or anyone who simply wants full control and auditability.

## What you’ll need

-   Azure App Service (Windows, .NET Framework 4.8 stack)
-   Azure Table Storage (a Storage Account)
-   A custom authorization app registered in your Azure AD tenant
-   Administrator permissions in both your Azure subscription and your Microsoft 365 tenant

If you can register an app in Azure, you can deploy this — and you can validate the whole thing in a non-production environment first.

## The full step-by-step guide

The complete walkthrough — adding the Web App, creating the Azure app registration, setting up the Storage Account, and configuring `web.config` — lives in our documentation, with screenshots for every step:

👉 [**Installing Virto Calendar in your own Azure**](https://docs.virtosoftware.com/docs/calendar-overlay-pro/administrators-guide-to-installation-and-configuration/installing-virto-calendar-in-your-own-azure/)

## Want a hand?

We offer enterprise licensing, custom integrations, white-label branding, and dedicated deployment support. If you’d like help setting this up in your environment, [book a demo](https://virtosoftware.pipedrive.com/scheduler/qlqoPwCM/book-a-demo) or reach out to our team.

Your environment. Your rules. Your calendar — fully under your control.

[Sergi Sinyugin](https://www.virtosoftware.com/author/svirtosoftware-com/)