Identity and access
Microsoft Entra ID, multi-factor authentication and Conditional Access. Privileged accounts are separated from everyday working accounts from the start, not after an incident.
Project · Microsoft 365
Microsoft 365,
configured
properly.
Subscribing to Microsoft 365 is a purchase. Configuring it securely is a project: identity, email, devices and sharing, to Microsoft best practice. Menshen runs that project in Angola, with a team certified as Microsoft 365 Administrator Expert.
What it is
The tenant built once, properly.
Microsoft 365 ships with generic defaults, designed to work for any organisation anywhere. They are fine to get started. They are not enough to protect the identities, devices and data of one specific organisation, with its own rules and its own risk.
This project closes that gap: Menshen configures the environment, validates it with a pilot group, rolls it out and hands it over documented. It suits a brand new tenant just as well as a tenant that was bought and never properly configured.
Delivered by Menshen's certified local team, on site in Luanda or remotely.
Scope
What gets configured
The exact scope is set during the survey and depends on the licences you hold. These are the areas an implementation project covers.
Exchange Online configured with Defender for Office 365 anti-phishing protection, and SPF, DKIM and DMARC aligned so your mail leaves and arrives trusted.
Devices
Microsoft Intune enrolment, compliance policies and app delivery. Access to data starts depending on the state of the device, not only on the password.
Collaboration and sharing
Teams, SharePoint and OneDrive with the structure and external sharing rules settled before users arrive. Rearranging this once the service is in use costs far more.
Adoption
Handover sessions for your team and materials in Portuguese. A correct configuration nobody knows how to use changes nothing at all.
Documentation
A record of what was configured and why, handed to your team at the end of the project. You keep the environment and the explanation of it.
How it runs
Four phases, with a pilot before the rollout
-
01
Scope
A survey of the current environment, user numbers, licences in force and the security requirements of your organisation. It produces a plan with phases, owners and windows.
-
02
Configuration
Building the tenant to the plan: identity, email, devices and sharing. Changes that affect users are made outside critical hours.
-
03
Validation
A pilot group uses the environment before it is rolled out to the whole organisation. Each area is checked against the reference best practices.
-
04
Handover
A handover session with your team, documentation delivered, and an agreed follow-up period as the project closes.
Where it fits
What usually comes before and after
Usually comes before
Email Migration
If you are coming off another mail system, migration handles the data. Implementation handles the environment that receives it.
Usually comes after
Health & Security Assessment
The independent check that the tenant is where it should be, using the same engine we run on any other environment.
To keep it there
Managed Services
A well-configured tenant drifts over time. Managed services keep the day-to-day operation running alongside your team.
Next step
Talk about your implementation
Tell us how many users you have, which licences you already hold and what is already running. From there we set the scope and the phases.