v0.8.88: Add Sync-AzLocalClusterUpdateSummary ("Check for updates" / checkUpdates) + stale-assessment auto-scan (#94)

* v0.8.85: consolidate setup workflow and align pipeline/version metadata

* test-run-timings

* v0.8.85 follow-up: delete ADO auth+inventory workflows and add merged ADO setup pipeline

* v0.8.85 follow-up: move collapsible subscription section into Export-AzLocalAuthValidationReport cmdlet; track test-run-timings.csv

* v0.8.85 follow-up: fix live integration test failures (Step.0 ErrorActionPreference, Step.3 path, Step.4 SummaryPath)

* Add test-run-timings.csv to repo (test performance metrics)

* docs: align pipeline appendix with Setup/Fleet naming

* chore: update test run timings

* v0.8.85: address PR #91 review findings - manifest, docs, mojibake, prune tests

- Get-AzLocalPipelineManifest: collapse legacy authentication-test +
  inventory-clusters rows into the merged setup-validate-and-inventory entry
- appendix-pipelines.md / README.md: replace removed filenames + old Step
  naming with Setup:/Fleet: numbering; fix section 13 file-layout block and
  section 14 reference; repair broken cross-doc anchors (README 8.1.1 ->
  #fleet-01, sideload.md -> #fleet-03); update present-tense Step.7 reference
- appendix-pipelines.md: reconcile Setup: 01 trigger docs to the shipped
  weekly Sunday 08:00 UTC cron
- fleet-update-status.yml: fix mojibake in YAML comment
- apply-updates-schedule.example.yml: replace Step.5/Step.7 with stable
  apply-updates.yml / Fleet: 04 references
- Tests: add 10 -PruneDeprecated regression tests (6 Copy- + 4 Update-)
  covering both-removed, single-removed, ID-mismatch-preserved, omitted-flag
  and -WhatIf paths

* docs: clarify sideload-catalog.example.yml header comment (v0.8.7 on-prem solution/SBE update sideloading)

* docs: fix grammar in sideload-catalog.example.yml header (introduce -> introduced)

* v0.8.86: rename onboarding pipelines Setup -> Config + clarify GitHub Environments are optional

- Rename the three onboarding workflow display names from `Setup: 0N` to
  `Config: 0N` (GitHub Actions `name:` and Azure DevOps `displayName:`/`name:`)
  so the Actions sidebar / ADO Pipelines list sorts the onboarding workflows
  ahead of the `Fleet: 0N` operational workflows (C sorts before F; the old
  `Setup:` prefix sorted after `Fleet:`). Display-name-only change - filenames,
  AZLOCAL-PIPELINE-ID values, aliases and prune logic are unchanged.
- Update bundled pipeline README.md + docs/appendix-pipelines.md (headings,
  cross-references, anchors, naming rationale) to the Config: NN naming.
- README.md (Automation-Pipeline-Examples): clarify that GitHub Environments
  are OPTIONAL. The branch-scoped federated credential is all OIDC needs, so a
  blank `environment` input is the supported minimal setup. Environments are a
  governance wrapper (approval gates, deployment-branch rules, wait timers,
  per-ring identities); environment-scoped federated credentials are only
  needed when a run actually names an environment. Mark the environment table,
  the inline + PowerShell env-scoped credential blocks, the subject-claim table
  row, and the section-5 secrets script accordingly.
- Version bump to 0.8.86: psd1 ModuleVersion + ReleaseNotes, psm1
  $script:ModuleVersion, CHANGELOG.md, both README files, docs/release-history,
  Tests version assertion, and all GENERATED_AGAINST_MODULE_VERSION pins across
  the bundled GitHub Actions and Azure DevOps templates.

Full Pester suite: 1266 passed, 0 failed, 1 skipped.

* ci: disable hosted Pester workflow (comment out pull_request + push triggers; keep workflow_dispatch). Suite is run locally before every push.

* v0.8.87: rename 'Orphan ARBs' section to 'Non-Azure Local and/or Orphan ARB appliances'

New-AzLocalFleetConnectivityStatusSummary (Fleet: 02) markdown output: rename the
Orphan ARBs section, add intro line, and expand the caveat to note that an Arc
resource bridge with no matching in-scope Azure Local cluster is NOT necessarily
orphaned - Arc resource bridge is also used by VMware vSphere and SCVMM. Adds
investigate-before-acting guidance. KPI note, causes list, and cluster-table
cross-reference updated to match. Output text only; no API or behavioural change.

Lock-step version bump 0.8.86 -> 0.8.87: psd1 (ModuleVersion + ReleaseNotes),
psm1 ($script:ModuleVersion), CHANGELOG, both README sections + appendix,
Tests assertion, docs/release-history.md, and all 20 GENERATED_AGAINST_MODULE_VERSION
pins. Full Pester suite green (1266 passed, 0 failed, 1 skipped, 38 not-run).

* v0.8.87: collapse Cluster Connectivity (with ARB Status) table by default

New-AzLocalFleetConnectivityStatusSummary now wraps the per-cluster Cluster
Connectivity (with ARB Status) table in a collapsed <details> block with an
'Expand to view clusters' summary, so the Fleet: 02 step summary stays compact.
Added a Pester assertion for the details/summary wrapper. Output text only; no
API or behavioural change. Release notes (psd1/CHANGELOG/README/release-history)
updated within the in-flight v0.8.87. Full Pester suite green (1267 passed,
0 failed, 1 skipped).

* v0.8.87: split Cluster Connectivity table into with/without connectivity issues

New-AzLocalFleetConnectivityStatusSummary now renders two per-cluster tables
instead of one:

- '### Cluster with Connectivity Issues' - clusters that are NOT (Connectivity =
  Connected AND ARB Status = Running). Shown first and expanded.
- '### Cluster without Connectivity Issues' - clusters that ARE Connected with a
  Running ARB. Collapsed behind an 'Expand to view clusters' details block.

Both tables share the same heading columns. Row rendering is factored into a
plain scriptblock (no .GetNewClosure()) reused by both tables. Added/updated
Pester assertions for both headings, the partitioning, and the collapsed block;
fixed the CSV-input context assertion that referenced the old single heading.

Release notes (psd1/CHANGELOG/README/release-history) updated within the
in-flight v0.8.87 (ReleaseNotes 9872 chars, under the 10000 limit). Full Pester
suite green (1270 passed, 0 failed, 1 skipped). Output text only; no API change.

* v0.8.87: rename bundled pipeline display names to Config:/Monitor:/Update: scheme

Renames all bundled pipeline display names (name: on GitHub Actions,
displayName:/name: on Azure DevOps) into a three-group single-digit scheme:
Config: 1-3 (onboarding/config), Monitor: 1-3 (day-2 fleet monitoring),
Update: 1-4 (update lifecycle), replacing the former Setup: 0N / Fleet: 0N
prefixes. Monitor: 2 is Fleet Health Status and Monitor: 3 is Fleet Update
Status so the numbering matches alphabetical order.

Display name only - filenames, AZLOCAL-PIPELINE-ID values, aliases, and
-PruneDeprecated logic are unchanged. Updates the bundled README,
appendix-pipelines.md (grouped/ordered conventions, alphabetical file layout),
ITSM docs, release docs, the manifest ReleaseNotes, CHANGELOG, the schedule
auditor's emitted markdown (Update: 4), and the matching Pester assertions.

Full suite green: 1282 passed, 0 failed, 1 skipped.

* v0.8.88: add Sync-AzLocalClusterUpdateSummary (Check for updates / checkUpdates)

Adds Sync-AzLocalClusterUpdateSummary (POST updateSummaries/default/checkUpdates) to refresh a cluster's update assessment - the programmatic 'Check for updates'. Fire-and-forget by default, -Wait polls lastChecked. Selectable ByName/ByResourceId/ByTag; SupportsShouldProcess.

Adds Private Test-AzLocalUpdateAssessmentStale detector (installed YYMM strictly behind manifest LatestYYMM) and wires an opt-out auto-scan into Export-AzLocalClusterUpdateReadinessReport (-SkipStaleAssessmentScan).

Surfaces 403/AuthorizationFailed from checkUpdates in the console (Status=AuthorizationFailed + RBAC warning naming the denied Action) so least-privilege custom-role gaps are visible. checkUpdates is preview and not yet in the provider operations catalog, so it cannot be added to the custom role - documented as a GA follow-up in module README, docs/rbac.md and Automation-Pipeline-Examples/README.md.

Option C: de-numbered remaining Step.N references in operator-facing output. Version bump 0.8.87 -> 0.8.88 (manifest, psm1, 21 pipeline YAML pins, CHANGELOG, ReleaseNotes, README). Export count 60 -> 61. Adds Pester coverage (suite 1303 passed, 0 failed).

Author: NeilBird

AzLocal.UpdateManagement/Automation-Pipeline-Examples/README.md

@@ -142,6 +142,8 @@ The identity created in section 4 needs the following permissions on every subsc
 
 If you opt in to the ITSM connector with Key Vault-sourced secrets, the identity additionally needs **Key Vault Secrets User** on the configured vault. No other new RBAC.
 
+> **Future RBAC - "Check for updates" (checkUpdates) auto-refresh (preview):** Since v0.8.88, `Sync-AzLocalClusterUpdateSummary` and the opt-out stale-assessment auto-scan in `Export-AzLocalClusterUpdateReadinessReport` POST the `Microsoft.AzureStackHCI/clusters/updateSummaries/default/checkUpdates` ARM action (the programmatic "Check for updates" button) on the `2026-03-01-preview` API. **This action is still preview and is NOT yet published in the `Microsoft.AzureStackHCI` provider operations catalog, so it cannot be added to a custom role definition today** (`az role definition update` validates `Actions[]` against the catalog and rejects unregistered actions). Until it GAs, an identity holding only the least-privilege custom role above will get a `403 AuthorizationFailed` on the refresh call - this is **non-fatal**: the cmdlets log the error and continue, and the readiness report still completes (it just cannot auto-refresh a stale assessment). To exercise the refresh today, assign the built-in **Azure Stack HCI Administrator** or **Contributor** role on the cluster scope, or skip the scan with `-SkipStaleAssessmentScan`. **When checkUpdates GAs, add the GA'd action (expected `Microsoft.AzureStackHCI/clusters/updateSummaries/checkUpdates/action` - confirm the exact string from a 403 `AuthorizationFailed` body or the provider operations catalog) to the `Actions[]` array in the role JSON below and to the permissions table above.**
+
 > **Tag-management identity (Manage UpdateRing Tags pipeline)** can use the built-in **Tag Contributor** role on its own - it grants exactly `Microsoft.Resources/tags/*` and nothing else. Since v0.7.65, `Set-AzLocalClusterUpdateRingTag` writes tags via the dedicated `Microsoft.Resources/tags/default` PATCH endpoint, so the broader `microsoft.azurestackhci/clusters/write` action (full cluster Contributor) is **not** required for tag changes.
 
 ### 3.1 Custom role: `Azure Stack HCI Update Operator (custom)`
@@ -194,6 +196,8 @@ The recommended MG default is shown in the JSON below. Whichever path you pick,
 
 `AssignableScopes` defaults to **one management-group scope** so the recommended MG + Azure Policy DINE path in [section 3.2](#32-recommended-assign-at-scale-via-azure-policy-dine-on-a-management-group) works out of the box (Azure custom roles can be assigned at or below any scope listed here). If you're following the legacy per-subscription path in [section 3.3](#33-manual--per-subscription-alternative-legacy), replace the entry with one or more `/subscriptions/<sub-id>` scopes instead - the hard cap is 2000 entries per role definition.
 
+> **Deliberately absent - `checkUpdates`:** the `Actions[]` array above does **not** include a `checkUpdates` action. The preview "Check for updates" auto-refresh (`Sync-AzLocalClusterUpdateSummary`) needs it, but the action is not yet in the `Microsoft.AzureStackHCI` provider operations catalog and `az role definition update` would reject it. See the **Future RBAC** note under the permissions table above. Add the GA'd action here once `checkUpdates` is generally available.
+
 **Who can run these commands?**
 
 Creating a custom role definition and assigning it are **separate, privileged Azure RBAC operations** - they are not granted by the new custom role itself. The user (or automation identity) running the commands needs the underlying RBAC actions in the table below at the scope listed in `AssignableScopes`.

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/apply-updates-schedule-audit.yml

@@ -87,7 +87,7 @@ parameters:
     default: false
 
 variables:
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.88'
   REQUIRED_MODULE_VERSION: '${{ parameters.moduleVersion }}'
   reportsPath: '$(Build.ArtifactStagingDirectory)/reports'
   # v0.8.7 sideload advisor defaults. Override at the pipeline / variable-group
@@ -215,7 +215,7 @@ stages:
       condition: always()
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.3-apply-updates-schedule-audit-report_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-apply-updates-schedule-audit-report_$(stamp.artifactStamp)'
         publishLocation: 'Container'
 
     - task: PublishTestResults@2

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/apply-updates.yml

@@ -129,7 +129,7 @@ variables:
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
   - name: GENERATED_AGAINST_MODULE_VERSION
-    value: '0.8.87'
+    value: '0.8.88'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).
@@ -247,7 +247,7 @@ stages:
             displayName: 'Publish Readiness Report'
             inputs:
               PathtoPublish: '$(Build.ArtifactStagingDirectory)'
-              ArtifactName: 'azlocal-step.7-apply-updates-readiness-report_$(stamp.artifactStamp)'
+              ArtifactName: 'azlocal-apply-updates-readiness-report_$(stamp.artifactStamp)'
               publishLocation: 'Container'
 
   # Stage 2: Apply Updates (with approval gate for production)
@@ -349,7 +349,7 @@ stages:
               source: 'current'
               # artifact name now carries a UTC timestamp - rebuild via the
               # readinessArtifactStamp variable mapped from the CheckReadiness stage.
-              artifact: 'azlocal-step.7-apply-updates-readiness-report_$(readinessArtifactStamp)'
+              artifact: 'azlocal-apply-updates-readiness-report_$(readinessArtifactStamp)'
               path: '$(Build.ArtifactStagingDirectory)'
 
           # v0.8.5 thin-YAML - readiness-gated apply via shared helper. Validates
@@ -417,7 +417,7 @@ stages:
             displayName: 'Publish Update Logs'
             inputs:
               PathtoPublish: '$(Build.ArtifactStagingDirectory)'
-              ArtifactName: 'azlocal-step.7-apply-updates-logs_$(stamp.artifactStamp)'
+              ArtifactName: 'azlocal-apply-updates-logs_$(stamp.artifactStamp)'
               publishLocation: 'Container'
 
           - task: PublishTestResults@2
@@ -485,7 +485,7 @@ stages:
             condition: and(always(), eq('${{ parameters.raiseItsmTicket }}', 'true'))
             inputs:
               PathtoPublish: '$(Build.ArtifactStagingDirectory)'
-              ArtifactName: 'azlocal-step.7-apply-updates-itsm-results_$(stamp.artifactStamp)'
+              ArtifactName: 'azlocal-apply-updates-itsm-results_$(stamp.artifactStamp)'
               publishLocation: 'Container'
             continueOnError: true
 

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/assess-update-readiness.yml

@@ -70,7 +70,7 @@ variables:
   # the version actually installed and to the latest on PSGallery, and emits a warning
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.88'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).
@@ -195,4 +195,4 @@ stages:
             condition: always()
             inputs:
               targetPath: '$(artifactsPath)'
-              artifact: 'azlocal-step.5-readiness-assessment-report_$(stamp.artifactStamp)'
+              artifact: 'azlocal-readiness-assessment-report_$(stamp.artifactStamp)'

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/fleet-connectivity-status.yml

@@ -110,7 +110,7 @@ variables:
   # the version actually installed and to the latest on PSGallery, and emits a warning
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.88'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).
@@ -210,7 +210,7 @@ stages:
       condition: always()
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.4-fleet-connectivity-status-report_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-fleet-connectivity-status-report_$(stamp.artifactStamp)'
         publishLocation: 'Container'
 
     # Publish JUnit test results AFTER the cmdlet (which writes the markdown
@@ -307,7 +307,7 @@ stages:
       continueOnError: true
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.4-fleet-connectivity-status-itsm-results_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-fleet-connectivity-status-itsm-results_$(stamp.artifactStamp)'
         publishLocation: 'Container'
 
     - task: PublishTestResults@2

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/fleet-health-status.yml

@@ -105,7 +105,7 @@ variables:
   # the version actually installed and to the latest on PSGallery, and emits a warning
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.88'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).
@@ -218,7 +218,7 @@ stages:
       condition: always()
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.10-fleet-health-status-report_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-fleet-health-status-report_$(stamp.artifactStamp)'
         publishLocation: 'Container'
 
     # Publish JUnit test results LAST so the Test Results tab is populated but the
@@ -322,7 +322,7 @@ stages:
       condition: and(always(), eq('${{ parameters.raiseItsmTicket }}', 'true'))
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.10-fleet-health-status-itsm-results_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-fleet-health-status-itsm-results_$(stamp.artifactStamp)'
         publishLocation: 'Container'
       continueOnError: true
 

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/fleet-update-status.yml

@@ -93,7 +93,7 @@ variables:
   # the version actually installed and to the latest on PSGallery, and emits a warning
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.88'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).
@@ -204,7 +204,7 @@ stages:
       condition: always()
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.9-fleet-update-status-report_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-fleet-update-status-report_$(stamp.artifactStamp)'
         publishLocation: 'Container'
 
     # Publish JUnit test results LAST so the Test Results tab is populated
@@ -311,7 +311,7 @@ stages:
       condition: and(always(), eq('${{ parameters.raiseItsmTicket }}', 'true'))
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.9-fleet-update-status-itsm-results_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-fleet-update-status-itsm-results_$(stamp.artifactStamp)'
         publishLocation: 'Container'
       continueOnError: true
 

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/manage-updatering-tags.yml

@@ -46,7 +46,7 @@ variables:
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
   - name: GENERATED_AGAINST_MODULE_VERSION
-    value: '0.8.87'
+    value: '0.8.88'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).
@@ -161,6 +161,6 @@ stages:
             displayName: 'Publish Log Artifacts'
             inputs:
               PathtoPublish: '$(Build.ArtifactStagingDirectory)'
-              ArtifactName: 'azlocal-step.2-updatering-tag-logs_$(stamp.artifactStamp)'
+              ArtifactName: 'azlocal-updatering-tag-logs_$(stamp.artifactStamp)'
               publishLocation: 'Container'
 

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/monitor-updates.yml

@@ -112,7 +112,7 @@ parameters:
     default: false
 
 variables:
-  GENERATED_AGAINST_MODULE_VERSION: '0.8.87'
+  GENERATED_AGAINST_MODULE_VERSION: '0.8.88'
   REQUIRED_MODULE_VERSION: '${{ parameters.moduleVersion }}'
   reportsPath: '$(Build.ArtifactStagingDirectory)/reports'
   # ITSM connector. When raiseItsmTicket=true the Raise ITSM task below
@@ -123,7 +123,7 @@ variables:
   # group reference convert this entire 'variables:' block to list form:
   #   variables:
   #     - name: GENERATED_AGAINST_MODULE_VERSION
-  #       value: '0.8.87'
+  #       value: '0.8.88'
   #     - name: REQUIRED_MODULE_VERSION
   #       value: '${{ parameters.moduleVersion }}'
   #     - name: reportsPath
@@ -219,7 +219,7 @@ stages:
       condition: always()
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.8-update-monitor_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-update-monitor_$(stamp.artifactStamp)'
         publishLocation: 'Container'
 
     - task: PublishTestResults@2
@@ -319,7 +319,7 @@ stages:
       condition: and(always(), eq('${{ parameters.raiseItsmTicket }}', 'true'))
       inputs:
         PathtoPublish: '$(reportsPath)'
-        ArtifactName: 'azlocal-step.8-update-monitor-itsm-results_$(stamp.artifactStamp)'
+        ArtifactName: 'azlocal-update-monitor-itsm-results_$(stamp.artifactStamp)'
         publishLocation: 'Container'
       continueOnError: true
 

AzLocal.UpdateManagement/Automation-Pipeline-Examples/azure-devops/setup-validate-and-inventory.yml

@@ -79,7 +79,7 @@ variables:
   # log if the YAML appears stale - prompting you to refresh via
   # Copy-AzLocalPipelineExample -Update. See Automation-Pipeline-Examples/README.md section 5.
   - name: GENERATED_AGAINST_MODULE_VERSION
-    value: '0.8.87'
+    value: '0.8.88'
   # Resolution order for the module version pin (leave all unset to install the latest,
   # which is the default "fix-forward" behaviour): queue-time parameter > pipeline variable
   # 'REQUIRED_MODULE_VERSION' overridden at queue time > empty (latest).
@@ -172,7 +172,7 @@ stages:
             condition: always()
             inputs:
               targetPath: '$(Build.ArtifactStagingDirectory)/auth-report'
-              artifact: 'azlocal-step.1-setup-auth-report_$(stamp.artifactStamp)'
+              artifact: 'azlocal-setup-auth-report_$(stamp.artifactStamp)'
               publishLocation: 'pipeline'
 
   - stage: Inventory
@@ -252,5 +252,5 @@ stages:
             displayName: 'Publish Inventory Artifact'
             inputs:
               PathtoPublish: '$(Build.ArtifactStagingDirectory)'
-              ArtifactName: 'azlocal-step.1-setup-cluster-inventory_$(stamp.artifactStamp)'
+              ArtifactName: 'azlocal-setup-cluster-inventory_$(stamp.artifactStamp)'
               publishLocation: 'Container'