DEV Community

Serguey Asael Shinder
Serguey Asael Shinder

Posted on

Your Deploy Script Signs In to Azure as a Person and Azure Now Wants That Person's Second Factor

Years ago
someone needed the release pipeline
to talk to Azure.

Service principals
looked complicated.

So they made a user.

deploy@yourcompany.

A password,
saved as a pipeline secret.

az login with a username
and a password.

It has deployed every release
since.

Nobody remembers
it is a person.

Azure has noticed.

Here is what changed.

Microsoft is making
multi-factor authentication
mandatory
for signing in to Azure.

Phase one,
from late 2024,
covered the portal.

Phase two,
rolling out from October 2025,
covers the Azure CLI,
Azure PowerShell,
infrastructure as code tools,
and REST calls
that create, change
or delete resources.

The rule is about identities,
not tools.

A user account
must pass a second factor.

A pipeline
has no phone.

So the deploy user
that has worked for six years
starts failing
on the next release.

Probably on a busy day.

The error will mention
multi-factor authentication.

The person reading it
will be the one
who never knew
the pipeline had a password.

Workload identities
are not affected.

Service principals.

Managed identities.

The things
that were always meant
to be robots.

This is the shape
of where things are going.

Systems are drawing a hard line
between people and software.

People get
second factors,
passkeys,
and sign-in checks.

Software gets
its own identity,
scoped to one job,
with no password
a person could type.

Accounts that pretend
to be both
are being squeezed out
from both sides.

What to do,
before the next release
finds out for you:

Search your pipelines,
scripts and scheduled jobs
for user logins.

Look for usernames
saved next to passwords.

Check the sign-in logs
for user accounts
signing in from build agents
at the same minute every night.

Move each one
to a service principal
or a managed identity,
with only the roles
that job needs.

Then disable the user.

Do not just change its password.

A login that runs
at three in the morning
with nobody awake
was never a person.

Stop giving it a person's name.

– Serguey Asael Shinder

Top comments (0)