INSIGHT DIRECT (UK) LTD

Microsoft Entra ID governance

Microsoft Entra ID Governance is an identity governance solution that enhances productivity, strengthens security, and facilitates compliance. It automates iden... Includes controls supporting secure and governed AI use.

Features

• 1. Automate the creation and maintenance of user identities.
• 2. Integrate with HR systems for streamlined onboarding and offboarding
• 3. Facilitates timely access provisioning and deprovisioning.
• 4. Access Lifecycle Management: Govern access changes over time.
• 5. Define policies for access modifications based on changes.
• 6. Automate workflows to handle critical
• 7. Control administrative privileges for users or groups.
• 8. Implement least-privilege principles to reduce risk.
• 9. Gain insights into access patterns and usage.
• 10. Monitor and audit access to critical assets.

Benefits

• 1. Automated identity lifecycle management
• 2. Access governance and compliance
• 3. Privileged access control
• 4. Increased visibility and auditing
• 5. Delegation to business groups
• 6. Cost-effective extension
• 7. Simplified processes and automation
• 8. Streamlined onboarding and offboarding
• 9. Enhanced security posture
• 10. Efficient access reviews.

• Education pricing available
• Free trial available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at pstenderteam@insight.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

364832229241209

Contact

Public Sector Tender Team
0344 846 3333
pstenderteam@insight.com

About your service

• Service categories:

  Systems Infrastructure Software

  Security

  • Security analytics
  • Governance, risk and compliance

  Identity and access management

  • Access
  • Privilege

  Data security

  • Digital trust
• Multi cloud support: Yes

Service scope

• Software add-on or extension: Yes
• What software services is the service an extension to: Extends Entra ID with lifecycle and access governance.
• Cloud deployment model: Public cloud
• Service constraints: Yes – typically licensed as Entra ID Governance / P2 add-on.
• System requirements: Service selection dictates system requirements; consult online pages for details.

User support

• Email or online ticketing support: Yes
• Support response times: "The Initial Response Time varies with both the support plan and the Business Impact of the request (also known as Severity). For a breakdown of initial response times by several level and business impact, please visit https://azure.microsoft.com/en-us/support/plans/response/; Weekend support availability varies depending on your Azure support plan. For more information, please visit https://azure.microsoft.com/en-us/support/plans/ "
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.2 AA
• Phone support: Yes
• Phone support availability: 24 hours, 7 days a week
• Web chat support: Yes
• Web chat support availability: 24 hours, 7 days a week
• Web chat support accessibility standard: WCAG 2.2 AA
• Web chat accessibility testing: We test all our services and support functions extensively with our customers and partner before release
• Onsite support: Yes, at extra cost
• Support levels: Microsoft provides four (4) Azure support plan options, which includes various levels of technical account management and cloud support engineering. The support options and cost include the following:; - BASIC (included for all Azure customers); - DEVELOPER ; - STANDARD ; - PROFESSIONAL DIRECT; - UNIFIED SUPPORT; For more information, visit https://azure.microsoft.com/en-us/support/plans/ and https://www.microsoft.com/en-us/unifiedsupport/overview
• Support available to third parties: Yes
• AI chatbot: Yes

Onboarding and offboarding

• Getting started: Azure users can start by creating an account at azure.microsoft.com and signing into the Azure Portal. New users get $200 credit for 30 days, plus 12 months of free popular services and 55+ always‑free services like Azure Functions and Storage. Starting is free, and users are only charged if they choose to move to pay‑as‑you‑go or exceed free usage limits
• Service documentation: Yes
• Documentation formats:
  • HTML
  • Other
• Other documentation formats:
  • Markdown (source files in GitHub)
  • JSON (schemas, ARM templates, REST metadata)
  • YAML (Bicep specs, some configuration references)
  • Code‑comment formats used to generate API docs
  • (XML, JSDoc, JavaDoc, Python docstrings)
• End-of-contract data extraction: Users can extract their data from Azure at the end of a contract by downloading it directly from Azure services such as Storage, SQL, or virtual machines using built‑in export tools, APIs, or Azure Storage Explorer. Logs and configurations can be exported from Azure Monitor or Log Analytics, and automated workflows can move large datasets to external locations before shutdown. After contract end, Azure provides a short grace period for data retrieval before resources are disabled and eventually deleted, ensuring users have time to securely back up or migrate all required data.
• End-of-contract process: When an Azure contract or subscription ends, Microsoft places the environment into a limited‑function state. Customers retain access to extract their data for approximately 90 days before deletion begins. Microsoft then disables the subscription and permanently deletes customer data no later than 180 days after expiration in accordance with the Online Services Terms and data‑handling policies
• Documentation accessibility standard: WCAG 2.2 AA

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
  • Opera
• Application to install: No
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: TBA
• Service interface: No
• User support accessibility: WCAG 2.2 AA
• API: Yes
• What users can and can't do using the API: Azure Resource Manager (ARM) API and Azure PowerShell let users create, modify, delete, and query Azure resources programmatically, just like the Azure Portal. They support automation, RBAC management, policy deployment, templates, and tagging. However, they cannot manipulate the Azure Portal UI, access portal-only preview features, or perform actions outside ARM’s control plane (e.g., interacting with VM guest OS, reading portal dashboards, or executing workloads). Both tools manage Azure resources—not the portal experience itself.
• API documentation: Yes
• API documentation formats:
  • Open API (also known as Swagger)
  • HTML
  • Other
• API sandbox or test environment: Yes
• Customisation available: No

Scaling

• Independence of resources: Azure limits noisy‑neighbor impact through strict resource isolation and governance. The hypervisor guarantees dedicated CPU and memory slices per VM; platform services enforce per‑tenant quotas and throttling; auto‑scaling and load‑balancing spread load across infrastructure; and continuous monitoring detects and mitigates contention. Combined, these controls ensure one customer’s demand doesn’t degrade another’s performance.

Analytics

• Service usage metrics: Yes
• Metrics types: https://learn.microsoft.com/en-us/azure/azure-monitor/reference/metrics-index
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
• Resource tagging: Yes
• FOCUS resource tagging: Yes

Resellers

• Supplier type: Reseller (no extras)
• Organisation whose services are being resold: Microsoft

Staff security

• Staff security clearance: Other security clearance
• Government security clearance: Developed Vetting (DV)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations:
  • United Kingdom
  • European Economic Area (EEA)
  • Other locations
• User control over data storage and processing locations: Yes
• Datacentre security standards: Complies with a recognised standard (for example CSA CCM version 4.0)
• Penetration testing frequency: At least every 6 months
• Penetration testing approach: In-house
• Protecting data at rest:
  • Physical access control, complying with CSA CCM v4.0
  • Physical access control, complying with SSAE-18 / ISAE 3402
  • Physical access control, complying with another standard
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
  • Other
• Other data at rest protection approach: Key management via Azure Key Vault; Encryption models such as envelope encryption and customer‑managed keys; Defense‑in‑depth physical and logical protections throughout the datacenter and service stack
• Data sanitisation process: Yes
• Equipment disposal approach: Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001
• Data sanitisation type:
  • Deleted data can’t be directly accessed / Cryptographic Erasure
  • Data Erasure
  • Explicit overwriting of storage before reallocation / Secure Erase
  • Degaussing
  • Physical Destruction / Hardware containing data is completely destroyed

Data importing and exporting

• Data export approach: As a customer, you maintain ownership of your data—the content, personal and other data you provide for storing and hosting in Azure services. Microsoft will not store or process customer data outside the geography you specify, except for certain non-regional services. You are also in control of any additional geographies where you decide to deploy your solutions or replicate your data.
• Data export formats:
  • CSV
  • Other
• Other data export formats:
  • CSV
  • JSON
  • XML
  • Parquet
  • GZIP
  • BZIP2
  • FOCUS (FinOps Open Cost & Usage Specification)
• Data import formats:
  • CSV
  • Other
• Other data import formats:
  • CSV, TSV, Delimited Text
  • JSON
  • XML
  • Parquet
  • Avro
  • ORC
  • GZIP, BZIP2 (Compression)

Data-in-transit protection

• Data protection between buyer and supplier networks:
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
• Other protection between networks: ExpressRoute private connectivity, keeping traffic off the public internet.; MACsec (IEEE802.1AE) encryption on ExpressRoute provider edges and across Microsoft’s backbone network.; Double encryption in transit (TLS + MACsec) for defense in depth.; Private Link, giving access to Azure PaaS services via private IPs in your VNet (no public exposure).; Service Endpoints, ensuring traffic to Azure services stays on the Azure backbone rather than the internet.; Internal datacenter-to-datacenter encryption, protecting all Azure east‑west traffic inside the cloud.; Zero Trust network validation, requiring continuous authentication and authorization for all connections.; DDoS protection Threat detection, preventing interception, tampering, or disruption of in‑transit data.
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway

Availability and resilience

• Guaranteed availability: Azure availability guarantees range from 95% to 99.99%, depending on:; ; Service type; Architecture (single instance vs. zone‑redundant); Storage redundancy configuration; Disk tier; ; The highest standard guarantee commonly offered is 99.99%, achieved when deploying VMs across multiple availability zones.
• Approach to resilience: Azure is designed to be resilient through distributed regions, Availability Zones, and redundant infrastructure, enabling workloads to withstand hardware, network, and datacenter failures. It incorporates fault isolation, multi‑region replication, and resilience-focused architectural patterns to maintain availability during disruptions. Azure’s Well‑Architected Framework emphasizes designing for resilience, recovery, and continuous operation so applications can detect, withstand, and recover from faults.
• Outage reporting: Azure reports outages through the public Azure Status page for broad, platform-wide incidents, providing a global view of service health. For personalized, subscription-specific issues, Azure Service Health delivers real-time notifications about service incidents, planned maintenance, and advisories via email, SMS, push notifications, or webhooks. Azure Service Health also shows impacted resources and updates until resolution.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
  • Other
• Other user authentication: Azure authenticates users through Microsoft Entra ID. When a user accesses the service, they are redirected to Entra ID, which verifies identity using methods such as passwordless sign‑in, MFA, certificates, or federated identity providers. Conditional Access policies may enforce requirements like MFA. Once authenticated, Entra ID issues a signed token, which the service validates before granting access based on the user’s permissions.
• Access restrictions in management interfaces and support channels: We restrict access to management interfaces and support channels using role‑based access control, ensuring only authorized personnel can perform administrative actions. Multi‑factor authentication, passwordless sign‑in, and Conditional Access policies enforce strong identity verification. Administrative endpoints are protected with network restrictions, logging, and continuous monitoring. Support channels require verified identity, limited privileged access, and follow least‑privilege and just‑in‑time access principles to minimize exposure.
• Access restriction testing frequency: At least every 6 months
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Username or password

Audit information for users

• Access to user activity audit information: You control when users can access audit information
• How long user audit data is stored for: User-defined
• Access to supplier activity audit information: You control when users can access audit information
• How long supplier audit data is stored for: User-defined
• How long system logs are stored for: User-defined

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: Yes
• Security governance standards:
  • CSA CSM version 4.0
  • ISO/IEC 27001
  • Other
• Other security governance standards: ISO 27001 (Information Security Management); ISO 27701 (Privacy Information Management); ISO 27018 (Protection of Personally Identifiable Information in the cloud); FedRAMP (U.S. government cloud security); DoD IL5 (U.S. Department of Defense cloud requirements); HIPAA / HITRUST (Healthcare data protection); PCI DSS (Payment card data security); GDPR compliance mechanisms
• Information security policies and processes: ISO/IEC 27001 Information Security Management System (ISMS); ISO/IEC 27002 Security Controls; ISO/IEC 27018 (protection of personal data in the cloud); ISO/IEC 27701 (privacy information management); SOC 1, SOC 2, SOC 3 audited controls; NIST SP 800‑53 security and privacy controls; NIST Cybersecurity Framework (CSF) alignment; FedRAMP security assessment and continuous monitoring; PCI DSS processes for cardholder data protection; GDPR-compliant privacy and data protection processes; Azure Security Development Lifecycle (SDL); Azure Policy governance and compliance enforcement; Continuous monitoring, logging, and threat intelligence processes
• Software Security Code of Practice: No

Operational security

• Configuration and change management standard: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Configuration and change management approach: Azure uses automated, auditable change management built on Azure Resource Manager. Changes are tracked through services like Microsoft.ChangeAnalysis, which records what changed, when, and by whom to detect configuration drift and support rapid incident resolution. Azure DevOps adds structured processes for identifying, reviewing, approving, and tracking changes using Agile best practices to minimise risk and ensure clear documentation and governance.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: We maintain a continuous vulnerability‑management program that includes automated scanning, threat intelligence monitoring, and rigorous patch management. Identified vulnerabilities are assessed, prioritised by severity and business impact, and remediated within defined SLAs. Our process includes regular penetration testing, configuration baseline reviews, and monitoring for zero‑day threats. Remediation activities are tracked to completion, with verification to ensure fixes are effective. We follow secure‑engineering practices, maintain incident‑response integration, and undergo independent audits aligned with recognised standards to validate the effectiveness of our controls.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: Azure protective monitoring involves continuously collecting, analysing, and correlating security signals across the cloud environment. It uses services like Azure Monitor, Defender for Cloud, Sentinel, and Activity Logs to detect anomalies, policy violations, and potential threats. Automated analytics identify suspicious behaviour, trigger alerts, and support incident response. Data is retained for auditing, investigation, and compliance, ensuring proactive detection and rapid mitigation of security risks.
• Incident management type: Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
• Incident management approach: Azure’s incident management process follows a structured lifecycle. Azure continuously monitors services to detect outages or security issues, then prioritises and analyses incidents to determine impact. Microsoft’s incident response teams isolate affected components, mitigate the issue, and restore normal operations. Throughout the event, Azure provides customer communications through the Service Health Dashboard. After resolution, Microsoft conducts post‑incident reviews to improve processes, strengthen detection, and prevent recurrence.
• Post-quantum cryptography secure: No

Secure development

• Approach to secure software development best practice: Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: Yes
• Description of free trial: New users get $200 credit for 30 days, plus 12 months of free popular services and 55+ always‑free services like Azure Functions and Storage. Starting is free, and users are only charged if they choose to move to pay‑as‑you‑go or exceed free usage limits.
• Link to free trial: https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account

Discount percentage by annual call-off contract value (excluding VAT)

• Less than £250,000: 0%
• Between £250,000 and £500,000: 0%
• Between £500,001 and £1,000,000: 0%
• Between £1,000,001 and £2,500,000: 0%
• Between £2,500,001 and £5,000,000: 0%
• Over £5,000,001: 0%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: Atlas
• ISO/IEC 27001 accreditation date: Sunday 13 April 2025
• What the ISO/IEC 27001 doesn’t cover: N/A
• ISO 28000:2022 certification: No
• ISO 9001 certification: Yes
• Who accredited the ISO 9001 certification: Atlas
• ISO 9001 accreditation date: Tuesday 1 April 2025
• What the ISO 9001 doesn’t cover: N/A
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Please provide your Cyber Essentials Certificate Number: Be7ce590-de10-486e-8431-2e10891a8979
• Cyber essentials plus: Yes
• Please provide your Cyber Essentials Plus Certificate Number: Cd8b1a78-44c7-4bb0-84d6-59a7506f3bba
• Other security certifications: No

Social value

• Section B - Commitment for Future: Delivery:

  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 1: Fair work: That offers fair wages and good working conditions. Help people get a job, stay in work, and progress in their careers, with good employment opportunities across the country. Notes: Where there is a large proportion of labour costs in the contract, commercial teams should consider MAC in Outcome 1 as a priority

    • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
    • Plans to engage the contract workforce in deciding the most important workplace issues to address
    • Ensuring new workers are informed of their right to join a trade union
    • Monitoring of employee engagement rates (by protected characteristic) and, where necessary, the development of actions to ensure all voices are heard across the diversity of the workforce
    • Employment contracts that reflect actual hours worked; steps taken to ensure employees understand their contracts and have the ability to review and adjust them if actual hours regularly exceed contracted hours
    • Activities that support an environment where staff are educated about, and feel empowered to, address their physical wellbeing
    • Activities that support an environment where staff are educated about and feel empowered to report and address bullying and harassment
    • Activities to cascade good practice on fair working conditions throughout the supply chain
    • Offer a pay and leave entitlement to all eligible staff who become kinship carers, ideally equivalent to statutory adoption pay and leave
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • Monitoring and reporting of gender and ethnicity pay gaps and plans to address them where necessary
    • Entitlement to sick pay for the contract workforce, with provision in place for any staff who do not meet the earnings threshold for statutory sick pay, payment of sick pay from day one of absence and payment of staff on the contract workforce who are off sick a replacement income of 100% of their usual earnings for as long as possible
    • Plans for an appropriate income replacement policy for staff who are required to spend time away from work to care for a sick dependent or close relative

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at pstenderteam@insight.com. Tell them what format you need. It will help if you say what assistive technology you use.