What Should Employees Do Before Changing Any Settings at Work?

```html

It sounds simple, right? You hit a snag with Microsoft 365 or Windows, you find a quick View website fix online, you tweak a setting, and voilà — problem solved. Well, if only fixing business IT issues were always that straightforward. More often than not, those quick fixes lead to bigger headaches, downtime, and sometimes security risks.

When it comes to business technology, especially critical platforms like Microsoft 365 and Microsoft Windows, a little ‘DIY troubleshooting’ can have outsized consequences. In this article, we’ll break down the essential steps every employee should follow before changing any settings at work. Think of this as your “STOP RIGHT THERE” checklist before you dive in.

Why You Should Exercise Caution Before Changing Settings

Before we dive into the checklist, let’s quickly cover why caution is so important:

Microsoft 365 and Windows environments are interconnected: A change in one spot can cascade and affect data access, permissions, or compliance. Settings changes can impact security: Disabling multi-factor authentication (MFA), unauthorized app integrations, or misconfigured policies put company data at risk. Business continuity is on the line: What may seem like a quick fix could cause outages for entire teams or departments. Many online tutorials and AI-generated scripts aren’t tailored for your environment: They may be outdated, inaccurate, or contain hidden destructive commands.

Common Traps With DIY IT Fixes

Let me save you some midnight troubleshooting calls by pointing out typical mistakes employees make when they try to fix IT issues on their own:

Following outdated or mismatched YouTube tutorials: The Microsoft 365 admin console changes frequently; a tutorial from two years ago might show options that no longer exist or have moved. Blindly trusting AI-generated answers or scripts: While generative AI is powerful, it doesn’t understand your specific tenant’s policies or constraints. An AI script may include commands that reset settings or delete data without warning. Disabling MFA or security controls "just to test": I can’t count how many times I’ve had to reset accounts because someone turned off MFA and forgot to turn it back on. This opens the door for potential breaches. Running scripts copied from forums or slack without reviewing: Scripts downloaded or copied from the internet can be harmful if you don’t understand what they do. Even well-intentioned scripts can remove critical configurations.

STOP RIGHT THERE: Your Pre-Change Checklist

Before making any change—big or small—ask yourself the following questions carefully. When in doubt, always check with your IT team.

What changed right before this started? Understanding the root cause is vital. Jumping to “fix” the symptom might break unrelated functionality. Have I documented the current state? Before changing any settings, take screenshots, export configurations, or write down the current values. Have I checked with IT? Your IT department or Managed Service Provider (MSP) has visibility across users and systems and can spot risky changes. Ask for approval or assistance. Did I verify the source of instructions or scripts? Cross-check tutorials against official Microsoft docs. Validate AI-generated solutions using trusted IT resources. Am I authorized to make this change? Confirm you have the necessary role or permissions. Unauthorized changes can violate company policy. Have I backed up any critical data? If the change touches files, permissions, or data retention, have contingencies in place. Did I plan for rollback? Know exactly how to undo the change if something goes sideways.

How To Document The Current State Properly

Documentation isn’t just a burden for IT folks; it’s your safety net. Here’s how to do it right:

Screenshots: Capture all setting pages/screens involved. This provides a visual record. Export configurations: Many Microsoft 365 settings and permissions can be exported into CSV or JSON. Check if you can export instead of copy-pasting. Write down exact values and options selected: Sometimes settings aren’t obvious or documented clearly. Record date and time: Helps correlate changes with incidents. Save scripts locally: If you plan to run a script, save a copy and review it line-by-line before execution.

Why You Must Always Check With IT

Your IT team is your friend here. Here’s why you should consult them every time:

IT has a holistic view: They understand dependencies across services and how your tenant or business workflows are configured. IT can authorize and delegate: Making unauthorized changes can have compliance or audit ramifications. IT can help with robust solutions: Many common problems already have approved fixes or automation built into the environment. IT owns backups and recovery: They can create snapshots or backups prior to changes.

Beware: AI-Generated Scripts and Answers

Let me be blunt: AI is a game-changer but it’s not a magic bullet. Here’s what you must keep in mind:

Always confirm the recommended solution against trusted sources: Use official Microsoft documentation, or consult a qualified admin. Read every line of AI-generated script: Don’t just copy-paste. Look for commands that delete users, groups, or modify critical policies. Test scripts in non-production environments: If you have access to a sandbox or test tenant, use it before running anything on production. Check for deprecated commands: Microsoft regularly updates PowerShell modules and APIs. Outdated commands might behave unpredictably.

Summary: Before You Click Run or Save

temporary access rules Step What To Do Why It Matters 1. Identify what changed before the issue started Trace root cause, avoid symptom fixes Prevents unnecessary or harmful changes 2. Document current configuration state Take screenshots, export settings Allows easy rollback if needed 3. Get IT approval Consult before making changes Ensures compliance and safety 4. Verify source of instructions or scripts Cross-check with official docs Avoids applying bad or outdated advice 5. Confirm authorization to change settings Check permissions and roles Prevents policy violations 6. Backup critical data Have recovery plan ready Mitigates risk of data loss 7. Plan rollback Know how to undo the change Minimizes downtime

Final Thoughts

When business IT breaks, it’s tempting to “just fix it” yourself. But remember: Microsoft 365 and Windows are complex enterprise-grade platforms, and every tenant is uniquely configured. Jumping in without a plan is how we end up chasing phantom bugs, lost data, and 2 a.m. pages.

Follow the checklist, rely on your IT team, and treat your environment like the critical asset it is. Your future self (and everyone else in your organization) will thank you.

So next time you encounter an issue, STOP RIGHT THERE, document the current state, check with IT, and get approval before changing a single setting.

```