Five Microsoft 365 admin settings to review
Review sharing links, external mail forwarding, app permissions, audit records and sign-in policies before changing your Microsoft 365 tenant.

Microsoft 365 settings can outlast the reason someone chose them. A sharing exception for a finished project, an old mail-forwarding arrangement or an unused app can remain after the people involved have moved on.
Ask your Microsoft 365 administrator to review these five areas. Record the current settings, the business need and the proposed changes before applying them. Tenant age alone doesn’t tell you whether a control is working.
1. Sharing links and external access
Check the organization settings and the settings on individual SharePoint sites and OneDrives. A permitted sharing level and the default link type are different controls: one sets the available choices; the other sets the choice staff see first.
Microsoft’s sharing guidance explains how those settings interact. Consider making Specific people the default for confidential work. Review existing broad links separately; changing the default doesn’t clean up every previous permission.
Test how a client or supplier will open a shared document. Remove links and guest access that no longer have a business purpose, while keeping a way for staff to work with people outside the business.
2. Automatic external mail forwarding
Find which outbound spam policy applies to each mailbox and whether it allows automatic forwarding outside the organization. Review mailbox forwarding, inbox rules and any other routes that send mail elsewhere.
Microsoft’s forwarding documentation warns that Automatic, System-controlled can behave differently between organizations. Have IT choose an explicit setting for your business and test it. Don’t assume that label means forwarding is blocked.
An old inbox rule doesn’t mean messages are leaving, either. Check the effective controls and forwarding reports. Document any permitted exception, its owner and the information it sends.
3. App permissions and user consent
Review the applications with permission to access mail, calendars or files. For each, identify its owner, purpose and requested access. Investigate unrecognized entries before revoking them; an integration may support billing or another important workflow.
Microsoft’s user-consent guidance covers policies for future consent requests. Reviewing those policies and reviewing existing grants are separate tasks. Don’t assume a stricter consent policy removed permissions granted earlier.
Keep a list of the apps you’ve agreed to allow, and give staff a way to ask for new ones. Publisher verification helps, but it can’t tell you whether an app needs the access it’s requesting.
4. Audit records you can retrieve
Ask IT to demonstrate a search for a recent sign-in or file-access event in the relevant logging service. Find out which activities are recorded, who can retrieve them and how far back each log goes.
Microsoft Purview’s retention documentation sets out licence-dependent periods. Audit Standard records generated from October 17, 2023 have a default retention of 180 days. Longer retention depends on the workload, policies and licences assigned to the people whose activities generate the records.
Don’t apply that period to every Microsoft log or treat it as a Canadian legal requirement. Set your investigation and record-keeping needs with the people responsible for privacy and compliance, then check whether your configuration meets them.
5. Sign-in policies and emergency access
Confirm how MFA is enforced for staff and administrators. Registration for MFA doesn’t by itself show that every important sign-in requires it.
Security Defaults provides a baseline. Conditional Access provides more configurable policies with the required licensing. Review policy coverage, exclusions and legacy authentication before changing either approach.
Prepare and test emergency access first. Microsoft’s emergency-account guidance includes phishing-resistant authentication and protection against policies that could prevent emergency sign-in. An exclusion needs a written reason and its own safeguards. It mustn’t leave an administrator account unprotected.
Make changes with an owner and a recovery plan
Prioritize the findings by exposure and business impact. Tell affected staff what will change, pilot where possible and keep a recovery route for access changes. Record who approved each exception and when it will be reviewed.
Keep the evidence with your tenant documentation. At the next review, IT can check what changed and whether those exceptions are still needed.


