Fix USGov cloud FinOps hub deployment time zone error (#2087)#2097
Open
RolandKrummenacher wants to merge 2 commits intodevfrom
Open
Fix USGov cloud FinOps hub deployment time zone error (#2087)#2097RolandKrummenacher wants to merge 2 commits intodevfrom
RolandKrummenacher wants to merge 2 commits intodevfrom
Conversation
Fixes #2087 - Add USGov (Virginia, Texas, Arizona, Iowa) and DoD (Central, East) region-to-timezone mappings so Data Factory schedule triggers activate successfully on Gov Cloud deployments. - Change the fallback time zone from the invalid display name 'Universal Coordinated Time' to the Windows time zone ID 'UTC'. - Add doc-link comments explaining the constraint so future region additions use the correct Windows time zone IDs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
microsoft-github-policy-service
bot
added
the
Needs: Review 👀
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #2087 — FinOps hub deployment to USGov Virginia fails with
ErrorCode=InvalidWorkflowTriggerRecurrence, ErrorMessage=The recurrence of trigger has an invalid time zone 'Universal Coordinated Time'.Two root causes in
timeZones.bicep:'Universal Coordinated Time'is the display name, not a Windows time zone ID. Per the ADF schedule trigger docs the valid ID isUTC.Changes
usgovvirginia,usgovtexas,usgovarizona(US Mountain Standard Time— no DST),usgoviowa,usdodcentral,usdodeast.'Universal Coordinated Time'to'UTC'.Test plan
bicep buildpasseseastus) and confirm no regressionNotes for reviewer
The ADF docs also state that when
timeZoneisUTC,startTime/endTimemust be suffixed withZ; for named zones they must not be. ThestartTimevalues in the consuming bicep files (e.g.'2023-01-01T01:01:00') have noZ, which matches the named-zone format. With USGov regions now mapping to named zones, the existing strings remain valid. A future region that falls through to theUTCfallback could trip this rule on trigger activation — out of scope for this fix, but worth tracking if we ever want triggers to work without an explicit mapping.🤖 Generated with Claude Code