> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/faq/cloud-platforms/azure.md). # Azure Common questions about running Tessell-managed databases on Microsoft Azure infrastructure. *** ### Q: How does Tessell provide services to databases running on Azure infrastructure? **A:** Tessell leverages **Azure Virtual Machines** and **Azure Managed Disks** for the data infrastructure. Two types of compute shapes are available: | Compute type | Azure shapes | Storage | | -------------------- | ---------------------- | ----------------------------------- | | **High-performance** | `Lsv3`, `Lasv3` series | NVMe local SSDs — unparalleled IOPS | | **Standard** | General-purpose shapes | Azure Premium SSDs or Ultra SSDs | Additional infrastructure details: * You can attach a **VNet of your choice** to the VM — either a public or private Azure Virtual Network. * The **Tessell Availability Machine** protects database data through regular snapshots and transaction log backups, stored using **Azure Snapshots** and **Azure Blob Storage**. *** ### Q: Is Tessell certified by Azure (Microsoft)? **A:** Yes. Tessell holds **three Azure certifications** that confirm production readiness on the Azure platform: | Certification | Meaning | | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Azure-preferred solution** | Listed in the [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/tessellinc1655919615020.tessell_database_service) as a preferred DBaaS | | **IP Co-sell Ready** | Microsoft sales teams can jointly sell Tessell with Azure services | | **MACC-eligible** | Purchases count toward your **Microsoft Azure Consumption Commitment** | *** ### Q: How does Tessell guarantee Zero Data Loss on Azure? **A:** The **Tessell Availability Machine** provides Zero Data Loss for Oracle databases. The data is protected by Availability Machine in three parts: 1. Snapshots: Snapshots are taken regularly with a minimum of one per day. 2. Archive Log Backups: Archive logs are backed up every 5 minutes. 3. Online/Redo Logs: Redo logs are multiplexed and kept on a Premium SSD. If a database failure occurs, Tessell can restore to the **last committed transaction** with the combination of the above three. *** ### Q: What High Availability and Disaster Recovery options does Tessell support on Azure? **A:** Tessell supports two levels of resilience on Azure: **Multi-AZ High Availability:** * Deploy a database in a **Multi-AZ configuration** — Tessell creates a standby instance in a different Azure Availability Zone. * The standby uses synchronous replication (Oracle Data Guard for Oracle; native streaming replication for PostgreSQL). * In the event of a primary failure, the standby is **automatically promoted** with no manual intervention. * A database proxy provides transparent connection failover so applications reconnect without code changes. **Cross-Region Disaster Recovery:** * Tessell supports snapshot and log replication to a second Azure region for full DR coverage. * A **global IP failover** redirects traffic to the DR instance automatically if an entire region becomes unavailable. *** ### Q: How does Tessell address the data security guidelines laid out by the RBI? **A:** Azure Cloud is an **RBI-certified Cloud Service Provider (CSP)**. Tessell additionally ensures RBI guidelines are met across the following areas: | RBI Requirement | Tessell Implementation | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Data Residency and Sovereignty** | Tessell is enabled for all **Azure India regions**; new regions are added as they become available | | **Access Controls** | With **VPT @ Customer**, databases are hosted inside the customer's own Azure account; with Tessell-hosted options (Professional/Business/VPT), network isolation and access restrictions are enforced by Tessell. In both cases, Tessell integrates with in-house **PAM and DAM** policies; no inbound connections from public IPs unless explicitly enabled | | **Data Encryption** | All databases are **encrypted at rest**; only **SSL connections** are enabled in transit | | **Backup and Disaster Recovery** | Multi-Region HA/DR with near-zero RPO meets RBI business continuity requirements; database-native backup gives banks freedom to choose long-term storage (cloud or physical datacenter) | Tessell's architecture ensures that auditing and compliance checks can be enabled seamlessly through the customer's own governance tooling. *** ### Q: How is Tessell integrated with other Azure Data Services such as Data Factory, Synapse Analytics, and Power BI? **A:** Tessell-managed databases on Azure integrate with the full Azure data ecosystem. Common integration scenarios: | Azure Service | Integration | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Azure Data Factory** | Use ADF data pipelines to ingest data from any source into — or out of — Tessell databases; schedule and orchestrate ETL/ELT workflows | | **Azure Synapse Analytics** | Use Tessell as a data source or destination in Synapse pipelines for data lake storage, warehousing, and transformations | | **Azure DB Link** | Establish secure cross-database connections (same or different subscriptions) and run cross-database queries directly against Tessell-hosted databases | | **Azure Stream Analytics** | Ingest and process real-time streaming data; persist processed results into Tessell for analysis or reporting | | **Azure Machine Learning** | Use Tessell as a training data source for Azure ML model builds | | **Azure Power BI** | Connect Power BI directly to Tessell databases as a data source; build interactive dashboards and reports | Because Tessell-managed databases expose standard connection strings, any tool that supports JDBC/ODBC connectivity can integrate with no additional configuration. *** ### Q: How can I migrate a database from on-premises to Tessell on Azure? **A:** Tessell provides **managed migration assistance** — you do not need to plan or execute the migration alone. **How the process works:** 1. The **Tessell Customer Success team** reviews your database (size, version, expected downtime tolerance, network topology). 2. They propose the optimal migration strategy — typically one of: * **Lift and shift** (minimal refactoring, accepted downtime window) * **Near-zero downtime migration** using engine-native replication tools (e.g., Oracle GoldenGate, PostgreSQL logical replication) 3. For workloads that require **upgrades or application refactoring**, Tessell works with **Azure Certified Partners** to provide additional advisory. --- # 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.tessell.com/tessell/faq/cloud-platforms/azure.md?ask=&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.