Create Pull Request
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-12 00:00 | #243 | cancelled |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Clean
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
## Adjusting the location Creating the profile in a new location is as simple as changing the `Location` property to our desired Azure Region. We also will need to create a new name for this profile. Let's change the name of the Configuration Profile `profileUk`. We should update the `Name` property within the profile, and also in the URL. We can use the `-replace` format operator to make this simple.
Now that we have changed the Location value, this updated Configuration Profile will be created in Western Europe when we submit it. ## Creating the new profile in the desired location All that remains now is to `PUT` this new profile, using `Invoke-RestMethod` once more.