[et_pb_section bb_built="1" _builder_version="3.17.6" custom_padding="0px||0px"][et_pb_row _builder_version="3.17.6"][et_pb_column type="4_4"][et_pb_text _builder_version="3.17.6"]

We have provided cloud solutions to asset managers for the past three years and in this time completed various types of email migrations to Office 365. These migrations include a mix of moving clients from an on-premise Exchange or a third-party legacy private cloud provider entirely to Office 365 to working with hybrid solutions that span both own on-premise and Office 365. 

During these migrations we noticed a range of issues with clients who opted to set up their Office 365 accounts via a more economical re-seller or through bundled packages with other services. 

Here are a few things to be wary of when setting up your Office 365 accounts with the wrong partner:

  1. Some of these providers offer what is called a “Syndication Tenant”. Microsoft retired this type of subscription but it is still offered by many existing re-sellers. With a Syndication Tenant agreement, the Office 365 account, Azure AD tenant and data is held by the re-seller and can’t be easily migrated away. In this setup, a multiple step process is required to hand over the account to another partner. The data needs to be backed up, the account deleted, and the data re-imported into a new account. All of this means extra complexity, user upheaval and extended downtime. 
  2. Some re-sellers, especially the syndicated tenant providers, do not offer the account holder true admin rights which means only a subset of the Office 365 functionality and management is available. 
  3. You could end up locked into a strict contract when negotiating your agreement. Sometimes your contract could last up to two or three years with no variations possible on the user services and license counts. 
  4. Security options are limited when compared to native Office 365 solutions or conditional access policies.
  5. Interface solutions from these re-sellers often lack basic functionality such as single sign on tools. 

With issues like these it is important to do your due diligence when exploring your options before committing. More likely than not you will find that your safest and most efficient option is to partner with a trusted and experienced service provider or go to Microsoft directly.

How Hentsū does it differently

We are a Tier 1 Microsoft Cloud Service Provider (CSP) and work directly with Microsoft. We are also a Silver partner and specialists in the asset management industry. All of this allows us to provide a range of flexible solutions tailored to the world of fund management. 

A good time to reach out to us is when your fund is about to be registered (SEC, FCA, etc). We know the industry requirements and can provide guidance on best practices and compliance. We also have the ability to work earlier with startups to ensure that they have all the tools in place from day one and can scale as they grow. 

Generally, we advise to take the following steps when setting up cloud services: 

  • Create a native Office 365 account through Microsoft directly, or use one of the Hentsū starter packages. We create client accounts directly with Microsoft so you hold the keys to the Azure AD tenant.  Your data is always your data so you can migrate to another provider at any time.  
  • Validate that you hold ownership over your Office 365 account and email domain. 
  • Purchase license subscriptions and set up users and groups.
  • Don’t go for 12 month commitments until you are sure of which services you actually need. We offer all of our clients the same 12 month discounts but on a monthly rolling basis. 
  • Set up data loss prevention and data retention policies and be aware of two factor authentication and mobile device security. We enable all these features by default as you on-board to our setup.

So be sure to carefully consider all the possibilities before signing on with Office 365 re-sellers or bundled solutions, as there are a range of options for your Office 365 needsIf you are unsure of where to go next for your Office 365 solutions, reach out today to learn how we can best support you. 

[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row _builder_version="3.17.6"][et_pb_column type="4_4"][et_pb_cta title="Talk to us about your Office 365 needs" button_url="https://hentsuprod.wpengine.com/contact" button_text="Contact Us Today" _builder_version="3.17.6"]

[/et_pb_cta][/et_pb_column][/et_pb_row][/et_pb_section]

Date/Time

Date(s) - 01/01/1970
12:00 AM - 12:00 AM

Location

600 5th ave. NY, NY
  • Quick and reliable public cloud deployments using Terraform
  • Enables users to describe public cloud environments in code
OK, the secret is out (our CTO Alex gave a talk about it, you can watch it below). One of the reasons Hentsū can deploy environments so quickly and reliably is because of the tools we’ve selected.  We’ve been using HashiCorp Terraform to describe, deploy and maintain public cloud environments since the company was founded. So we were glad to see Microsoft recently announced a multi-year partnership with HashiCorp to enhance the Terraform Provider for Azure. This is great news for Terraform users, like Hentsū, who have already benefited from using the Infrastructure as Code method of provisioning.

What Exactly is Terraform?

Terraform enables us to describe public cloud environments in code (HashiCorp Language). Terraform can then compare a public cloud account to the code and create a plan of changes to bring the environment up to date. If the plan is acceptable it can then be applied by Terraform to create, update or delete infrastructure resources such as networks, routing tables, firewall rules and virtual machines. It does this rapidly with as much parallelisation as possible leading to a slick, reliable and iterative way of deploying and maintaining public cloud environments. Deploying additional environments (test, staging, production) becomes a copy & paste exercise, or we create reusable modules. Using a code versioning system, like Git, we can version control a public cloud environment and even rollback to a previous version if, for example, a firewall rule change didn’t have the desired result. Changes can be codified on a separate code branch, and a pull request and approval required to promote changes to the master branch. This makes for a robust change management workflow for business-critical production environments. The code commit history provides an audit trail of who changed what, and the commit notes describe why. Terraform requires administrative credentials to make changes to public cloud environments. Storing these securely is a challenge so we prefer to generate short lived credentials that are usable for maximum 1 hour. Also, as part of a release pipeline, a scheduler like Teamcity or Jenkins can apply approved changes on behalf of IT and development teams.

Hentsū and Terraform

Microsoft backing HashiCorp only confirms that using Terraform to provision resources on cloud platforms is becoming the standard way of deploying infrastructure. Hentsū has first-hand experience using the software to deploy infrastructure successfully for its clients.

How Hentsū can Help

Want to discuss using Terraform software to deploy onto the cloud? Contact us at: hello@hentsu.com

Date/Time

Date(s) - 01/01/1970
12:00 AM - 12:00 AM

Location

600 5th ave. NY, NY

Hey you; get off of my (public) cloud

It appears the UK regulator might want to rewrite those famous Stones lyrics. It has truly been refreshing to see the Financial Conduct Authority (FCA) adopt such a progressive attitude towards cloud services. Regulatory guidance or consultations typically precipitate a collective sigh from the market. But the FCA’s guidance consultation 15/6 issued last November was instead met with universal approval. Many even claimed it would pave the way for financial services companies to take advantage of cloud computing services. Cloud architectures and delivery models have naturally long been championed by IT professionals. But, with the FCA clarifying that it doesn’t object to the use of a public cloud per se, the floodgates truly have been opened. Of course the guidance comes with a caveat. The regulator insists firms must continue to comply with regulations such as Systems and Controls (SYSC). But, caveats aside, this is pretty progressive. It is also helpful in cementing the regulator’s position as a supporter of innovation. Our industry has often been hamstrung by decades of technical debt and a desire to maintain the status quo. Surely having a regulator take an active stance in promoting and fostering innovation is to be applauded? This follows in the older news of other financial regulators embracing, publicly approving or even themselves using the public cloud, for example Singapore and FINRA. The European Union Agency For Network And Information Security (ENISA) had a good summary in their recent report, covering also the Dutch and Swiss regulators.

FCA Cloud Guidance - the Risks and Considerations

That said, adopting cloud services is not without risk. It is therefore absolutely right that the published guidance documents a detailed list of factors firms should take into account before doing so. It is imperative that any solution is implemented correctly. The guidance offers a comprehensive, but by no means a prescriptive list of all those factors that need to be considered. These include: legal and regulatory, risk management, international standards, provider oversight, access to data and business premises, outsourcing supply chains, change management processes, business continuity and resolution plans, and finally vendor risk. Encouragingly the FCA offers constructive guidance within each of those categories. For example, given that some cloud service providers keep the location of their data centres a guarded secret (for security reasons), the FCA acknowledges that “service providers may, for legitimate security reasons, limit access to some sites – such as data centres.” Even so, not having physical access to a data centre, does not prohibit firms from complying with audit obligations to provide access to certain data sets. We believe the FCA is showing both a pragmatic and progressive approach towards cloud adoption and is in our opinion a new chapter for financial technology. And it is already materialising on the ground with a wave of recent or imminent announcements of big adoptions of public cloud computing from some established names across the spectrum of financial services. To understand more about our managed cloud services visit //hentsuprod.wpengine.com/why-hentsu/ As fans of the Rolling Stones, we just had to include an obligatory picture: A cloud tribute to the Rolling Stones

Date/Time

Date(s) - 01/01/1970
12:00 AM - 12:00 AM

Location

600 5th ave. NY, NY
  Hentsū, the specialist hedge fund managed services provider, is proud to announce the upgrade of our AWS consulting partner status to APN Standard Consulting Partner. As an AWS Consulting Partner with our financial services pedigree we are ideally placed to help hedge funds of all sizes design, architect, build, migrate and manage their workloads and applications on AWS.Hentsū is now APN Standard Consulting Partner, helping deliver AWS consulting and solutions to hedge funds

Hentsū and AWS Consulting

Hentsū was "born in the cloud", and since our inception we have worked closely with AWS to deliver specialist hedge fund solutions, which leverage the full benefits of AWS. We hold official AWS certifications and Hentsū consultants have been working with AWS since 2010. We have the necessary skills and technical knowledge to design, deploy and manage complex solutions on the AWS platform. We combine this deep technical expertise with decades of trading and asset management experience, to bring unique value to the projects we deliver. This partner tier upgrade is recognition of the built-in Hentsū AWS skills and capabilities. Find out more about from the Amazon Partner Network site.

Hentsū Cloud Services

Hentsū can help you leverage cloud platforms to drive innovation and business agility. The focus is not just about reducing your costs, but also about increasing system performance and scalability. Migrating complex trading systems to the cloud requires careful analysis and planning, the right architecture and a detailed migration process. For early migrations we work through proof of concepts to identify risks, effective approaches and build team skills and confidence. We use proven methodologies such as the AWS Cloud Adoption Framework, with additional workflows and approaches specific to financial services.

Hentsū Cloud Solutions

Hentsū delivers cloud solutions which are fully compliant with FCA, SEC & CFTC rules and regulations. We embed by default the security, disaster recovery (DR) and business continuity (BCP) expected in critical fund management environments. Our tooling and experience is cloud agnostic across AWS, Azure and Google, to help deliver the best solutions for our customers.

Date/Time

Date(s) - 01/01/1970
12:00 AM - 12:00 AM

Location

600 5th ave. NY, NY