Colour theme
Book a consultation

Keeping cloud configuration under control

Give cloud settings an owner, write down the settings you want and review access and configuration changes before they create unwanted exposure.

A 3D rendering of a key in the keyhole of a metal, cloud-shaped lock.

A cloud application can be available within minutes, while decisions about access, sharing and administration remain unfinished. Those decisions need an owner after the first setup, too.

Microsoft’s shared responsibility guidance explains that responsibilities vary by service model. A supplier managing infrastructure doesn’t remove your responsibility for the business data, identities and configuration you control.

Use six checks to make those responsibilities concrete.

1. Know which services are in use

List the services the business has chosen, their business owners, administrators and the information they handle. Ask staff where work is happening outside that list. Give them a quick way to ask for a new tool to be added.

Include connected applications and integrations. An integration can expose information even when the app itself looks locked down.

2. Separate administration from daily work

Review who can change access, sharing and security settings. Give each person only the privileges their role needs, and keep a documented emergency administrator account.

Test the effects of reducing a role before changing production. Fewer administrators shouldn’t leave you with one unavailable person and no recovery route.

3. Write down the settings you want

Record the intended sign-in requirements, external sharing rules, logging and recovery settings. Explain exceptions and who approved them. Include a review date.

Where the platform can enforce a setting, such as requiring MFA through Conditional Access, use it, and check which licences and apps it covers. A sensitivity label doesn’t automatically prevent copying in every app or on every device.

In Microsoft 365, Microsoft Secure Score lists recommended settings and shows which ones you’ve applied. Use it as a checklist to compare against your baseline.

4. Review what users can reach

Test a staff account, a guest account and an integration against a sample of real records. Check inherited permissions, existing sharing links and exports.

A settings screenshot helps, but test the access too. Record expected and observed results so the next reviewer can repeat the check.

5. Track significant changes

Decide which events need review: a new administrator, wider sharing, a changed sign-in rule or a new integration. Check that the service logs those events and that someone receives and follows up on alerts.

Where automated alerts aren’t available, schedule a documented comparison with the baseline. Don’t count on an alert you haven’t set up and tested.

6. Close the loop

Prioritize findings by the records and workflows affected. Assign changes, check their effect and update the baseline. Keep recovery access available during the work.

Repeat the review after a significant application change or ownership handoff. Our cloud and Microsoft 365 reviews can help turn an initial setup into a maintained configuration.


Featured Image Credit