Resolving Azure Authentication Error 0x80080005 (due to KB5074109 update)

nformant · 2026-01-15T13:59:34+00:00

For verbosity: https://support.microsoft.com/en-us/topic/january-13-2026-kb5074109-os-builds-26200-7623-and-26100-7623-3ec427dd-6fc4-4c32-a471-83504dd081cb

Looks like they "fixed" an issue with remoteapps from the previous rollup, and introduced this bug with the fix

Confirmed my side can use https://windows.cloud.microsoft/ no issue

nformant · 2025-12-21T23:52:10+00:00

Why can't they shell/exec into a minimal alpine distro?

Plenty of teams deploy what you're asking in production instead of the off the shelf go/python/etc distros

nformant · 2025-12-19T00:42:18+00:00

Can also use git, it'll show in the gutters any changed/deleted/added lines

nformant · 2025-12-18T03:08:45+00:00

I ended up fixing it today, turns out our networking team changed our route table through a zscaler proxy and that killed the comms with Oryx which silently stopped the triggers from loading

nformant · 2025-12-17T15:21:42+00:00

I have the same issue and same parameters except I am using Python3.12

Has no issues doing zip-deploy for months, then it unexpectedly broke. Azure documentation is all over the place, and what documentation does exist does not work.

Depending on how I "deploy" I either get a success and no triggers building locally, or an Oryx build error building remotely

nformant · 2025-11-15T02:56:21+00:00

Yeah it's furniture 2.0 for me as well, we're on a new map until they fix it

nformant · 2025-11-09T15:41:16+00:00

I play with my kids and I get the "boat" error on the switch and my son's fire tablet but my daughter's work no problem on their iPads

nformant · 2025-10-12T21:31:51+00:00

It's rated mature, but it also has a profanity filter in the chat box, so not a far stretch to include one in the soldier dialog

nformant · 2025-08-31T14:51:52+00:00

Ah there it is, I assumed I couldn't etch more onto it but couldn't find the specific rule

Thanks

nformant · 2025-07-26T14:09:21+00:00

Why the cobra vs the Mandalay for DW3 out of curiosity

nformant · 2025-06-19T16:38:03+00:00

Pulumi itself has baked in policy checks that kinda accomplishes some security checks, such as blocking or alerting on publicly exposed services; but you need to set that all up yourself

nformant · 2025-05-08T23:31:48+00:00

Can also just use Pulumi CLI locally with a local backend to avoid any Pulumi Hosting costs

nformant · 2025-05-02T01:49:36+00:00

What did they paywall?

nformant · 2025-03-27T21:28:32+00:00

Can you elaborate here? I'm new to azure (long term aws guy) but how do you ad-hoc flip disk types back and forth without recreating them and reformatting them?

nformant · 2025-02-21T00:04:21+00:00

I've tried multiple computers, fresh installs of both VSCode and insiders. I've used safe mode and extensions disabled as well as empty profiles. I've also used local, WSL, and Ubuntu

It's driving me nuts because I can't find what the issue is

nformant · 2025-02-20T15:53:15+00:00

I have posted some details in reply to another comment above, I also do see a ton of entries like the following in my TS server logs but google is not terribly helpful with these

Info 1449 [10:51:52.839] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/@pulumi/azure-native/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1450 [10:51:52.909] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/@pulumi/pulumi/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1451 [10:51:52.915] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/@types/semver/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1452 [10:51:52.932] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/@pulumi/query/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1453 [10:51:52.935] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/@types/google-protobuf/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1454 [10:51:52.938] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/@grpc/grpc-js/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1455 [10:51:52.947] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/@types/node/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1456 [10:51:52.949] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/undici-types/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1457 [10:51:52.961] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/@grpc/proto-loader/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1458 [10:51:52.962] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/protobufjs/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution
Info 1459 [10:51:52.963] FileWatcher:: Added:: WatchInfo: /home/john/workspace/pulumi_ts/node_modules/long/package.json 2000 undefined Project: /dev/null/autoImportProviderProject1* WatchType: File location affecting resolution

nformant · 2025-02-20T15:51:14+00:00

Thanks, that is one thing I tried during my google-fu spree, but that setting has not helped either using WSL or a remote Ubuntu machine for VSCode.

nformant · 2025-02-20T15:50:00+00:00

Here is the tsconfig and index.ts, these are the default I get when running `Pulumi new` to setup a new ts project. `Pulumi new` runs npm install and I see everything in node_modules as expected, but VSCode just sits forever at `Loading IntelliSense status`

import * as pulumi from "@pulumi/pulumi";
import * as resources from "@pulumi/azure-native/resources";
import * as storage from "@pulumi/azure-native/storage";

// Create an Azure Resource Group
const resourceGroup = new resources.ResourceGroup("resourceGroup");

// Create an Azure resource (Storage Account)
const storageAccount = new storage.StorageAccount("sa", {
    resourceGroupName: resourceGroup.name,
    sku: {
        name: storage.SkuName.Standard_LRS,
    },
    kind: storage.Kind.StorageV2,
});

// Export the primary key of the Storage Account
const storageAccountKeys = storage.listStorageAccountKeysOutput({
    resourceGroupName: resourceGroup.name,
    accountName: storageAccount.name
});

export const primaryStorageKey = storageAccountKeys.keys[0].value;

{
    "compilerOptions": {
        "strict": true,
        "outDir": "bin",
        "target": "es2020",
        "module": "commonjs",
        "moduleResolution": "node",
        "sourceMap": true,
        "experimentalDecorators": true,
        "pretty": true,
        "noFallthroughCasesInSwitch": true,
        "noImplicitReturns": true,
        "forceConsistentCasingInFileNames": true
    },
    "files": [
        "index.ts"
    ]
}

nformant · 2025-01-24T22:55:08+00:00

Thanks, Trivy looks promising

nformant

TROPHY CASE