Timmothy Green

Working through deploying this. Suggest removing the recommendation to delete the Sharepoint site if the deploy.ps1 fails and instead just allow the script to overwrite on the next run. If...

> Hey folks, just adding my 2c - been talking over this with @SteveMutungi254 since May and then it got kinda forgotten for a while, as I mistakenly popped the...

> Ok, weird. I started doing a bit of testing in my Azure tenant tonight. Brand new linux VM with a managed service identity that has the `DNS TXT Contributor`...

I found this: https://www.thomasmaurer.ch/2022/10/use-the-azure-arc-managed-identity-with-azure-powershell/ I can use 'Connect-AzAccount -Identity' and get a token, but from that article it appears that to get an access token via REST for an Arc-enabled...

The sample script from that article does get me a token 

I pulled that and got the below  I found the line and updated the api version to the latest supported version '2021-02-01'. Then I got this  I'm noticing...

I was able to get it working. In Line 497 (requesting the token) it was missing the authorization header. I added some code adopted from that sample script. This works...

The Azure Connected Machine agent runs as this ""C:\Program Files\AzureConnectedMachineAgent\himds.exe" and also includes a CLI tool azcmagent which has commands like 'azcmagent show' or 'azcmagent version'

I tried the new Azure.ps1 but wasn't working for me I had to make some edits. This is working for me. ``` try { $tokResponse = Invoke-RestMethod $metadataUri -Body $body...

``` DEBUG: Loading PAOrder list from disk DEBUG: Creating new 2048 order with domains: removed, removed DEBUG: ACME Header: { "nonce": "lQjHBKQCcoetdrOxP9rPUirase46kUCxHEyX5XiFZ3yamQv4q4w", "kid": "https://acme-staging-v02.api.letsencrypt.org/acme/acct/190603734", "alg": "ES256", "url": "https://acme-staging-v02.api.letsencrypt.org/acme/new-order" } DEBUG:...