Portfolio

Azure Tenancy Split for Leo Regtech

egforit splits tenancy and eliminates downtime for SaaS company

Read how we helped Leo Regtech split up their Azure tenancy in two. We were able to grant their wish and separate the two accounts with zero interruption in service for their development team and maintain essential info and history.  

Executive brief

Dividing departments and data

Leo Regtech is a Cairo-based software company specialising in compliance software to enable businesses to comply with the FCA Handbook, AMF regulations, and GDPR, or tailor their software to match specific compliance needs.

After realising they needed extra support splitting up their singular Azure tenancy, they discovered egforit Software and our track record for success with Azure and decided to enlist the best.

The Challenge

Create a new tenancy

The company was restructuring and needed their resources, docs, and essential info to be split into a separate tenant for the new arm/branch of the company.

The main goal for the client was to complete the project with zero interruption or degradation in service for their development team. They also needed to ensure that their sensitive management information and project commit history were secure.

The Solution

An efficient split

Leo Regtech wanted to focus on reducing day-to-day regulatory burdens on teams, allowing them to be more forward focused, leading to enhanced operational processes.

After analysing the structure of their existing Azure tenancy, we devised a plan to migrate their Azure DevOps and Azure Subscriptions to a new tenant and active directory.

The approach meant we could deliver a result within a timely manner and deliver on our promise of zero downtime or degradation of service.

The Results

Zero downtime, maximum results

After working through various phases of unit testing, integrated testing, geo-redundant storage, and failover groups – we were successful in our goal of zero downtime. Meaning the development team could keep working efficiently, effectively, and without fear of losing their work.

Leo Regtech also saved a significant amount of money on their licence fees by purchasing through our Microsoft CSP.

Over the next few months, we’ll be regularly checking-in with the team to make sure they’ve truly hit the ground running.

Looking for Azure experts?

Our team of Microsoft experts have over 10 years experience helping customers get ahead of the competition. Kickstart your modernisation journey today and get in touch.

Info

8th August 2023

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by egforit.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress,
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
-id-[app_id],-session-[add-id]

×