Use managed identity for secrets when domain joining Azure Files

[doherty100]

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ X ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

The current bootstrapping process passes secrets to a virtual machine extension in order to domain join Azure Files. This results in secrets being stored locally on jumpwin1.

Any log messages given by the failure

N/A

Expected/desired behavior

Use of managed identities to retrieve secrets at runtime would avoid storing secrets locally on jumpwin1.

OS and Version?

Windows Server 2022

Versions

AzureSandbox v2.10.0

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.