Menu

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

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

DEV Community: azure·Serguey Asael Shinder·about 2 hours ago
#G7gIYwiN
#devtoazure#devto#dev#user#azure
Long article (337 words) — no AI summary yet.
Reading 0:00
15s threshold

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…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.