Feature guides
Customer-Controlled Azure Deployment
Run Hirebase in the client’s own Microsoft Azure tenancy, with the client retaining control of its cloud environment and participating in access and governance design.
Explore 40 questionsThe short answer
What matters for your decision
Hirebase supports client Azure tenancy, cloud governance, identity, and operational ownership. The organization defines its process and Hirebase is configured for that implementation; the practical fit is strongest when teams need a connected workflow across hourly or distributed operations.
Keep deployment in the client environment
Hirebase runs as a single-tenant deployment inside the client's own Azure tenancy. Identify the target subscription, resource hierarchy, and change approvers before deployment so the cloud team knows what it owns.
Align identity and access
Bring cloud and identity owners into scope for roles, access, network policy, and identity integration. Customer control requires active administration: define who provisions administrators, reviews access, and investigates cloud alerts.
Plan integration and operations
Map APIs, payroll systems, and file exchanges crossing the Azure boundary, then review endpoints and credentials with IT. Distinguish inbound and outbound flows and agree how secrets, logs, and configuration changes are governed.
Evaluate the tradeoffs honestly
Azure resource organization has valid isolation patterns with different tradeoffs. Confirm region and service availability, support boundary, and operating cost. Review backup, retention, incident response, and offboarding expectations; customer-controlled hosting is not itself a compliance certification.
Place the application inside the client's Azure boundary
Hirebase's architecture page describes a dedicated, single-tenant deployment within the client's own Microsoft Azure tenancy, including application and database resources in that environment. The client retains cloud control and participates in identity, access, network, and key governance.
Agree the shared operating responsibilities
Customer-controlled deployment makes the client's cloud team part of the operating model. Confirm subscription prerequisites, Azure service availability, identity groups, network paths, monitoring, backups, deployment access, support escalation, and offboarding ownership for the proposed environment.
Hirebase for your operation
Make the workflow fit your business.
Connect workforce workflows with organization-wide licensing, configurable operating rules and customer-controlled Azure deployment. Bring your site requirements, worker journey and integration needs to an implementation conversation.
Evaluate HirebaseYour buying questions
Questions, answered
40 of 40 questions
What does this workflow cover for customer-controlled azure deployment?
The Customer-Controlled Azure Deployment workflow in Hirebase connects client Azure tenancy, cloud governance, identity, and operational ownership in a shared operational record. The exact steps depend on the client implementation.
Link to this answerWho typically owns this process for customer-controlled azure deployment?
Operations leaders usually define the process, with supervisors, HR/payroll, and IT contributing where their work or controls are affected.
Link to this answerWhat information should be ready before rollout for customer-controlled azure deployment?
Map the current roles, records, exception paths, approval owners, and downstream systems first. This gives the implementation team a concrete process to configure and validate.
Link to this answerHow does the workflow start for customer-controlled azure deployment?
The process starts with the operational event—such as a worker being assigned, a shift being completed, or a record needing review—and uses client Azure tenancy, cloud governance, identity, and operational ownership as its context.
Link to this answerWhat happens when an exception occurs for customer-controlled azure deployment?
The team should define an owner and a review path for exceptions. Hirebase records operational activity and configurable approvals; it does not remove the need for a responsible reviewer.
Link to this answerCan managers review and correct records for customer-controlled azure deployment?
Yes. The relevant manager review and correction steps can be configured for the client's workflow. Preserve the original event and make the adjustment reason clear to reviewers.
Link to this answerHow does this connect with scheduling for customer-controlled azure deployment?
Scheduling can use client Azure tenancy, cloud governance, identity, and operational ownership where the configured workflow requires it, helping operations connect planned work with what happened in the field.
Link to this answerHow does this connect with attendance for customer-controlled azure deployment?
Attendance records provide the actual event details that can be reconciled with client Azure tenancy, cloud governance, identity, and operational ownership; each deployment determines which verification steps apply.
Link to this answerHow does this connect with payroll for customer-controlled azure deployment?
Hirebase calculates wages from attendance and approved time data, then hands the result to the payroll provider the organization uses. Payroll disbursement remains with that provider.
Link to this answerCan requirements differ by client or site for customer-controlled azure deployment?
Yes. Hirebase is configured around client workflows, so roles, thresholds, and steps can vary where the implementation defines those differences.
Link to this answerDoes Hirebase replace our existing payroll processor for customer-controlled azure deployment?
No. Hirebase calculates pay; the existing payroll provider remains responsible for processing and disbursing it. Statutory filing is not performed by Hirebase.
Link to this answerCan teams exchange data with other systems for customer-controlled azure deployment?
Hirebase supports REST APIs, webhooks, and CSV/XLSX exchange. Named enterprise ERP integrations may require client-specific engineering; confirm the exact system and data contract during scoping.
Link to this answerWhat should operations measure for customer-controlled azure deployment?
Choose measures tied to the purpose: completeness, turnaround time, exceptions, approval aging, and whether the downstream handoff reconciles. Set definitions with the process owner.
Link to this answerHow can supervisors use the records for customer-controlled azure deployment?
Supervisors can use the operational record to see status, spot open exceptions, and route work to the next owner. Access should follow the client's role design.
Link to this answerWhat should workers be told for customer-controlled azure deployment?
Explain which information is collected, when it is collected, who reviews it, and how workers can raise a correction or question. Follow the organization's policies and applicable law.
Link to this answerCan the process support multiple locations for customer-controlled azure deployment?
The platform supports distributed operations. Site structures, permissions, and local process differences should be agreed as part of the deployment design.
Link to this answerWhere is Hirebase deployed?
Hirebase is deployed as a single-tenant installation inside the client's own Microsoft Azure tenancy.
Link to this answerWho owns the Azure subscription and cloud bill?
The client controls its Azure environment and subscription; Azure resource consumption and commercial responsibilities should be agreed in the deployment scope.
Link to this answerDoes customer-controlled deployment remove all security work?
No. The client still needs to govern identity, access, network controls, keys, monitoring, and operational support for its environment.
Link to this answerCan client IT review access and network boundaries?
Yes. The deployment model is intended to involve the client's cloud and identity owners in access and network design.
Link to this answerCan data be deployed in a chosen Azure region?
The architecture is designed for Azure deployment; confirm the requested region and service availability with Hirebase during technical scoping.
Link to this answerDoes Azure tenancy by itself prove regulatory compliance?
No. Customer-controlled hosting is an architectural choice, not a certification or legal compliance determination.
Link to this answerIs the implementation a self-serve SaaS signup?
No. Customer Azure deployment requires technical scoping and coordination with the organization's cloud and identity stakeholders.
Link to this answerWhat should an architecture review cover?
Review tenancy and subscription prerequisites, identity, access, network routes, data flows, integrations, backup/operations, and support boundaries.
Link to this answerWho controls Azure identities and access?
The client retains control of its cloud environment and should define the identity, role, access-review, and administrator processes with its IT team.
Link to this answerDoes the client control encryption keys?
The architecture page describes customer-managed encryption keys through Azure Key Vault. Confirm the design and responsibilities for the proposed deployment with IT.
Link to this answerDoes customer tenancy establish a specific compliance certification?
No. Hirebase should not be represented as holding certifications based only on its hosting model. Customer Azure controls and legal obligations must be assessed separately.
Link to this answerCan the client choose any Azure region worldwide?
The architecture describes global technical deployability, but region and service availability must be confirmed for the specific deployment and Azure configuration.
Link to this answerWho manages network access to the instance?
The client's cloud and network owners govern access boundaries and should agree how application users and integrations reach the deployment.
Link to this answerDoes client-hosted deployment remove the need for Hirebase support?
No. Define the support model, access needed for maintenance, change approvals, monitoring responsibilities, and incident coordination between the client and Hirebase.
Link to this answerWhat happens to access at contract end?
Offboarding and data-retention steps should be specified in the contract and deployment plan, including account removal, export, retention, and deletion responsibilities.
Link to this answerIs the Hirebase deployment single tenant?
The architecture page describes dedicated application and database resources inside the client's Azure tenancy.
Link to this answerWho owns the Azure subscription?
The client's organization owns and controls its Azure environment. Resource consumption and commercial responsibility should be stated in the deployment scope.
Link to this answerDoes the client's cloud boundary remove all Hirebase access?
No. The deployment and support model should specify any access needed by Hirebase and how the client approves and governs it.
Link to this answerCan the client use Microsoft Entra ID?
The architecture page describes integration with Microsoft Entra ID for role-based access and SSO. Validate the exact identity configuration in technical scoping.
Link to this answerDoes Azure tenancy prove a security certification?
No. Hosting architecture alone is not a certification or legal compliance determination.
Link to this answerWho governs encryption keys?
The architecture page describes customer-managed keys through Azure Key Vault. Confirm the proposed key ownership and operating procedure with IT.
Link to this answerCan any Azure region be selected?
The page describes global technical deployability, but the target region and service availability must be confirmed for the specific implementation.
Link to this answerWhat should an architecture workshop cover?
Review tenancy, subscription, identity, access, network paths, integration endpoints, monitoring, recovery, support, and offboarding responsibilities.
Link to this answer