Azure4Sure provide a comprehensive Azure design and support service, and optionally an Azure managed service including the tenant and all contained infrastructure. We provide incident, request, change, capacity and problem management.
- 24hr proactive monitoring and alerting.
- Load balancing, clustering, high performance compute.
- Azure automation & scripted failover, failback & bursting routines/runbooks.
- Mix of host replication and geo-resilience for maximum assurance.
- Isolated or routed network connectivity, load balancing, reserved IP addressing.
- Encrypted connectivity and storage.
- Connectivity via public or private connected routes, WAN, MPLS, VPN.
- Hosts Linux and Windows servers.
- Native integration with SQL Server technologies.
- Integrated seamlessly with your on premise IT infrastructure.
- Fully integrated with your on premise IT infrastructure.
- Can be refined to integrate with your business application needs.
- Simple to monitor and maintain.
- Low cost, pay as consumed, highly flexible.
- Reduce your infrastructure costs.
- Minimise downtime with dependable recovery.
- Easily provides reports to your review your infrastructure status
- Easy to access via terminal server, VPN, Azure Domain Join.
- Flexible performance to meet business requirements.
- Maintain your security using storage and connectivity encryption.
£11.64 per instance per month
|Email or online ticketing support||Email or online ticketing|
|Support response times||Support for DRaaS is available 24x7.|
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||WCAG 2.0 AA or EN 301 549|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||No|
|Onsite support||Onsite support|
We can provide 24/7/365 incident management based on pre-agreed SLAs.
A technical account manager provide support where needed, engineering resources can be accessed 24/7/365 as required.
|Support available to third parties||Yes|
Onboarding and offboarding
Azure4Sure will provide documentation referencing both official Microsoft literature but also lessons learned from previous deployment and experiences. Additionally you can review official microsoft literature at:
https://azure.microsoft.com/en-us/resources/ & https://docs.microsoft.com/en-us/azure/
|Other documentation formats||Microsoft Office based documentation as necessary.|
|End-of-contract data extraction||Users/customers are able to extract their operational systems data from any Azure hosted using traditional methods such as file copy via network shares, recovery from Microsoft Azure Backup Server or using ASR to migrate their server instances from Azure to their on premise solutions. the customer also has the option of utilising the Azure Import/Export services shown here: https://azure.microsoft.com/en-gb/pricing/details/storage-import-export/|
Please see: https://www.microsoft.com/en-us/trustcenter/privacy/you-own-your-data
Microsoft contractually commits to specific processes when a customer leaves a cloud service or the subscription expires. This includes deleting customer data from systems under our control.
If you terminate a cloud subscription or it expires (except for free trials), Microsoft will store your customer data in a limited-function account for 90 days (the “retention period”) to give you time to extract the data or renew your subscription. During this period, Microsoft provides multiple notices, so you will be amply forewarned of the upcoming deletion of data.
After this 90-day retention period, Microsoft will disable the account and delete the customer data, including any cached or backup copies. For in-scope services, that deletion will occur within 90 days after the end of the retention period. (In-scope services are defined in the Data Processing Terms section of our Online Services Terms.)
Using the service
|Web browser interface||Yes|
|Using the web interface||Azure comes with a feature rich and powerful user interface within the Azure Resource Manager console, we can help you configure additional services through this interface and provide the necessary training. All configuration is undertaken through the management console using a mix of graphical user interface, powershell commands and runbook scripting.|
|Web interface accessibility standard||WCAG 2.0 AA or EN 301 549|
|Web interface accessibility testing||Please see this link for more information: https://www.microsoft.com/en-us/accessibility/|
|What users can and can't do using the API||Customers are able to utilise the Azure API Management service to create their own API's as needed. The Azure Service Management API which provides programmatic access to much of the functionality available is through the Management Portal available here https://msdn.microsoft.com/en-us/library/azure/ee460799.aspx|
|API automation tools||
|API documentation formats||HTML|
|Command line interface||Yes|
|Command line interface compatibility||
|Using the command line interface||Azure CLI 2.0 is optimized for managing and administering Azure resources from the command line, and for building automation scripts that work against the Azure Resource Manager. See https://docs.microsoft.com/en-us/cli/azure/install-azure-cli|
|Independence of resources||Microsoft Azure cloud utilises various Cloud Scale techniques and technologies, to ensure multi-tenant services are not affected in terms of peak usage, additionally the Azure hypervisor is designed with 3 principles in mind to ensure high performance 1) Efficient and designed to work hardware as much as possible 2) Small footprint to ensure less code churn and less reboots 3) Tightly integrated with the Windows Azure Kernel to support best performance levels.|
|Infrastructure or application metrics||Yes|
|Other metrics||ASR replication metrics|
|Supplier type||Reseller providing extra features and support|
|Organisation whose services are being resold||Microsoft|
|Staff security clearance||Conforms to BS7858:2012|
|Government security clearance||Up to Developed Vetting (DV)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||
|User control over data storage and processing locations||Yes|
|Datacentre security standards||Complies with a recognised standard (for example CSA CCM version 3.0)|
|Penetration testing frequency||At least once a year|
|Penetration testing approach||Another external penetration testing organisation|
|Protecting data at rest||
|Other data at rest protection approach||Please refer to: https://azure.microsoft.com/en-gb/blog/azure-site-recovery-encryption-at-rest/ , http://download.microsoft.com/download/0/D/D/0DD8FB12-6343-4A50-80B2-545F2951D7AE/MicrosoftAzureDataProtection_Aug2014.pdf , https://docs.microsoft.com/en-us/azure/storage/storage-service-encryption|
|Data sanitisation process||Yes|
|Data sanitisation type||
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Backup and recovery
|Backup and recovery||Yes|
|What’s backed up||
|Backup controls||Users/customers can create different backup routines across VM instances or resources or create protection groups to apply specific backup routines to groups of resources. Any variety of backups can be applied to either Azure or On Premise resources.|
|Scheduling backups||Users schedule backups through a web interface|
|Data protection between buyer and supplier networks||
|Data protection within supplier network||
|Other protection within supplier network||Azure virtual networks can be segregated by dedicated VPN and firewall rules. Data can be transferred between Windows Server 2016 instances and security enforced using firewall rules, encryption and various authentication solutions. Various third party provided IDS solutions can be implemented to further improve security.|
Availability and resilience
|Guaranteed availability||Please refer to this document for exact information: https://azure.microsoft.com/en-us/support/legal/sla/site-recovery/v1_1/|
|Approach to resilience||
Azure is an extremely resilient hyper-scale cloud platform that includes many resilience solutions, these include: storage, virtual machine, application and network high availability across multiple data centres and geographies. Additionally ASR can be utilised to provide resilience between Azure data centres and Azure to physical on premise data centres.
Please see https://www.microsoft.com/en-us/cloud-platform/global-datacenters and https://www.microsoft.com/en-us/TrustCenter/
|Outage reporting||Please see https://azure.microsoft.com/en-us/status/ and https://portal.azure.com/#blade/HubsExtension/ServicesHealthBlade|
Identity and authentication
|Other user authentication||
Shared key between on premise and Azure based ASR infrastructure.
Authentication hinges on the use of Azure Active Directory, this can be run in isolation of federated with your internal on premise Active Directory.
|Access restrictions in management interfaces and support channels||Azure-AD can designate separate administrators to serve different functions. These administrators will have access to features in the Azure portal and, depending on their role, will be able to create or edit users, assign administrative roles to others, reset user passwords, manage user-licenses, and manage domains, among other things. A user who is assigned an admin role will have the same permissions across all of the cloud services that your organization has subscribed to, regardless of whether you assign the role in the Office365 portal, or in the Azure classic-portal, or by using the Azure-AD module for Windows PowerShell.|
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||
|Devices users manage the service through||
Audit information for users
|Access to user activity audit information||Users have access to real-time audit information|
|How long user audit data is stored for||Between 6 months and 12 months|
|Access to supplier activity audit information||Users receive audit information on a regular basis|
|How long supplier audit data is stored for||Between 6 months and 12 months|
|How long system logs are stored for||Between 6 months and 12 months|
Standards and certifications
|ISO/IEC 27001 certification||Yes|
|Who accredited the ISO/IEC 27001||Bsi|
|ISO/IEC 27001 accreditation date||20/06/2017|
|What the ISO/IEC 27001 doesn’t cover||Please see https://www.microsoft.com/en-us/trustcenter/compliance/iso-iec-27001|
|ISO 28000:2007 certification||No|
|CSA STAR certification||Yes|
|CSA STAR accreditation date||12/02/2018|
|CSA STAR certification level||Level 3: CSA STAR Certification|
|What the CSA STAR doesn’t cover||None|
|Who accredited the PCI DSS certification||Coalfire|
|PCI DSS accreditation date||01/04/2016|
|What the PCI DSS doesn’t cover||None|
|Other security certifications||Yes|
|Any other security certifications||
|Named board-level person responsible for service security||Yes|
|Security governance certified||Yes|
|Security governance standards||
|Other security governance standards||Microsoft Azure complies with the 14 Cloud Security Principles - See https://gallery.technet.microsoft.com/14-Cloud-Security-Controls-670292c1 . Also FACT, NHS IG Toolkit, FedRamp, NIST 800-171, EU Model Clauses|
|Information security policies and processes||
Azure4Sure operates a security officer post who is responsible for security policies and procedures. Any security issues/breaches/incidents and reported and immediately via the companies incident management systems and managed through according to severity, impact and scope.
Microsoft Azure performs annual ISMS reviews, the results of which are reviewed by management. This involves monitoring ongoing effectiveness and improvement of the ISMS control environment by reviewing security issues, audit results, and monitoring status, and by planning and tracking necessary corrective actions.
Also see https://www.microsoft.com/en-us/TrustCenter/Compliance/ISO-IEC-27001 and The Microsoft Cloud Security Policy is available via the Service Trust Platform
|Configuration and change management standard||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Configuration and change management approach||
Azure4Sure operates ITIL aligned change and configuration management procedures.
Azure has developed formal standard operating procedures (SOPs) governing the change management process. These SOPs cover both software development and hardware change and release management, and are consistent with established regulatory guidelines including ISO 27001, SOC 1 / SOC 2, NIST 800-53, and others.
Microsoft also uses Operational Security Assurance (OSA), a framework that incorporates knowledge gained through capabilities that are unique to Microsoft including the Microsoft Security Development Lifecycle (SDL), the Microsoft Security Response Center program, and deep awareness of the cybersecurity threat landscape.
Please see https://www.microsoft.com/en-us/SDL/OperationalSecurityAssurance and https://www.microsoft.com/en-us/sdl
|Vulnerability management type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Vulnerability management approach||
Azure4Sure fully utilises the Azure vulnerability management solutions, these include:
- Azure security assessment center to assess threats to service: https://azure.microsoft.com/en-gb/services/security-center/
- The use of 'as a service' solutions to utilise the Microsoft capability to apply patches to services.
- The use of Microsoft reporting aswell as trusted third parties to provide alerting on vulnerabilities.
Vulnerability scans are performed on a quarterly basis at a minimum. Microsoft Azure contracts with independent assessors to perform penetration testing of the Microsoft Azure boundary.
|Protective monitoring type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Protective monitoring approach||
Azure4Sure utilises Microsoft Security Center to provide a comprehensive security alerting solution.
Each alert is reported and logged within the Azure4Sure incident management platform.
Each alert is assessed and inline with its impact level.
|Incident management type||Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402|
|Incident management approach||
Azure4Sure operates a ITIL aligned incident management procedure.
Incidents related to the platform are automatically alerted via monitoring and alerting.
Users can report incidents into the Azure4Sure incident management platform online or via email, or phone.
Reports can be provided to customers as agreed.
|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 v3.0)|
Separation between users
|Virtualisation technology used to keep applications and users sharing the same infrastructure apart||Yes|
|Who implements virtualisation||Supplier|
|Virtualisation technologies used||Hyper-V|
|How shared infrastructure is kept separate||
Please see https://www.microsoft.com/en-us/TrustCenter/Security/default.aspx
|Price||£11.64 per instance per month|
|Discount for educational organisations||No|
|Free trial available||Yes|
|Description of free trial||All features are included for a period of 31 days before you must convert to a paid subscription.|
|Link to free trial||https://azure4sure.co.uk/azure|
|Pricing document||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|