microsoft / microsoft/Microsoft-Fabric-workload-development-sample

Regarding workload region

Open
#268 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
58
Forks
39
PR merge metrics
No merged PRs in 30d

Description

Workload Manifest Schema Version (if relevant)

No response

Your Question

Our workload will initially only support 4 regions. My question relates to how we can provide our workload to customers whose tenant does not reside in 1 of those 4 regions. Am I correct in assuming that the region of the capacity to which a workspace is associated determines the regional location of assets within that workspace?

That said, a customers whose tenant is located in US-Central (not a target regision for our workload) could purchase a capacity in US-West and associate it to a workspace. With that association, all data placed in the workspace would reside on a storage container in US-West. Is this correct?

Follow-up question... If a workspace's capacity is changed to a capacity from a different region, is the data moved?

Context / Background

SAS Decision Builder workload provides workload support with region aks clusters.

Additional References

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the workload's regional AKS cluster setup and the documented relationship between capacities, workspaces, tenants, and storage regions. Confirm whether capacity region determines asset location and whether changing capacity moves existing data; document the answers and any applicable limitations.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
cloud, infrastructure
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.