Knowledgebase

Microsoft Technology in Practice: Common Mistakes Print

  • microsofttechnology, microsoft, dns, domain, backup, hacked, permissions, guide
  • 0

What goes wrong repeatedly.

NO EMERGENCY ACCESS ACCOUNT

A policy then locks out every administrator.

MULTI-FACTOR AUTHENTICATION NOT ENFORCED

The commonest route to compromise, and entirely preventable.

LEGACY AUTHENTICATION LEFT ENABLED

Which bypasses the protection you configured.

LICENCES ASSIGNED TO PEOPLE WHO LEFT

Billed monthly, indefinitely.

TREATING SYNCHRONISED STORAGE AS BACKUP

Until a deletion or encryption propagates.

UNCONTROLLED CREATION OF TEAMS AND SITES

Producing sprawl nobody can navigate.

BREAKING PERMISSION INHERITANCE EVERYWHERE

So nobody can establish who can see what.

BUILDING IN THE DEFAULT POWER PLATFORM ENVIRONMENT

With no governance and no path to production.

IGNORING DELEGATION WARNINGS

Producing applications that silently return wrong results at scale.

DOMAIN MEMBERS POINTED AT PUBLIC DNS

Breaking authentication in ways that appear unrelated.

RESOURCES LEFT RUNNING IN AZURE

The largest single source of avoidable cost.

SECRETS IN CONFIGURATION AND SCRIPTS

Which end up in version control history permanently.

WHAT PREVENTS MOST OF THESE

Governance decided early, applied consistently, and reviewed.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot