The walkthrough was written by AWS's Peter Sarpong, Haneesh Kotha and Paul Morosin. It depends on a feature that has been available for most of this year. AWS's official announcement says it has made AWS IAM Identity Center multi-Region support generally available. With it, you can replicate your workforce identities, permission sets, and other metadata in your organization instance of IAM Identity Center connected to an external identity provider (IdP), such as Microsoft Entra ID and Okta. Third-party coverage dates that general availability to February 3, 2026.
The rest of this piece walks through the setup and points out where the AWS blog post and AWS's own administration guide differ.
The architecture in one paragraph
Entra ID syncs users and groups to one primary IAM Identity Center instance. That instance is encrypted with a customer-managed multi-Region AWS KMS key and replicated to each Region where you run WorkSpaces. Windows Autopilot user-driven mode handles the Entra join and Intune enrollment. AWS Secrets Manager stores the Entra application credentials in each Region. Each WorkSpaces directory points at the Identity Center replica in its own Region, so sign-in stays in that Region.
The AWS announcement explains why this matters for desktop services. Applications deployed in additional Regions access replicated workforce identities locally for optimal performance and reliability.
Summary: you keep one identity source and one SAML/SCIM integration, and each Region has its own replica. Administration still runs through the primary Region.
Before you start: licensing, versions and Region limits
The AWS blog lists only an AWS Organizations account, an Entra tenant with Global Administrator access, and Intune licensing. AWS's WorkSpaces Administration Guide adds several requirements:
- Entra licensing: Microsoft Entra ID P1 or higher, with Entra ID and Intune enabled and roles assigned.
- Roles: Intune Administrator to manage Autopilot deployment profiles, and Global Administrator to grant admin consent for the app's API permissions.
- Windows licensing: Windows 10/11 VDA E3 or E5 per-user subscription licenses for WorkSpaces users. BYOL must be enabled on the AWS account, with a valid Windows 10 or 11 image imported.
- Supported Windows versions: Windows 10 21H2 and 22H2, and Windows 11 Enterprise 22H2, 23H2, 24H2 and 25H2.
- Protocol: Entra ID directories support only the DCV streaming protocol.
- Unsupported tenants: Entra tenants in GCC High and DoD environments.
- Regions: Entra-joined Personal WorkSpaces are offered everywhere WorkSpaces is, except Africa (Cape Town), Israel (Tel Aviv) and China (Ningxia).
Identity Center replication has its own Region limits. These have changed during the year, so check them before you design anything. At launch, AWS said the feature was available in the 17 enabled-by-default commercial AWS Regions for organization instances of IAM Identity Center connected to an external identity provider. A later AWS update says you can now replicate IAM Identity Center to opt-in AWS Regions, and between Regions within the AWS GovCloud (US) and AWS China Regions.
GovCloud users should note a separate limit. The WorkSpaces guide says cross-Region integration between WorkSpaces and Identity Center is not supported in the AWS GovCloud (US) Region. Identity Center replication support in GovCloud does not change what WorkSpaces itself supports.
On cost, AWS says standard AWS KMS charges apply for storing and using CMKs. IAM Identity Center is provided at no additional cost.
Step 1: Create the primary Identity Center instance and connect Entra ID
- In your AWS Organizations management account, open the IAM Identity Center console in the Region you want as primary. The walkthrough uses us-east-1 as its example.
- Choose Enable, then Multi-Region instance to create an organization instance. Record the Instance ARN and Identity Store ID.
- Go to Settings → Identity source → Actions → Change identity source → External identity provider, and download the Identity Center SAML metadata file.
- In the Microsoft Entra admin center, choose Enterprise applications → New application, search for AWS IAM Identity Center, and configure SAML-based sign-on with that metadata file.
- Under Provisioning, turn on automatic provisioning. Enter the Identity Center SCIM endpoint as the Tenant URL and its access token as the Secret Token. Select the users and groups to sync, then start provisioning.
- Confirm that the users appear in Identity Center with the correct attributes.
Choose the primary Region carefully. AWS's Identity Center resiliency documentation says the primary Region cannot be changed after you enable the service. The blog suggests picking the Region closest to your Entra tenant, but that is a recommendation, not a requirement.
Things that commonly go wrong at this stage:
- UPN limits. WorkSpaces identifies users by their Entra UserPrincipalName. A UPN can't be longer than 63 characters. If you change a UPN after a WorkSpace is assigned, that user can't connect until you change it back. Check for long UPNs and planned renames before go-live.
- Sync validation errors. The WorkSpaces guide warns that Entra users missing a first name, last name or display name will fail to sync, with validation errors on fields like
name.givenName. - Scale. The blog gives a default limit of 200,000 users and says to request a quota increase if you need more.
- Member-account directories. If you create directories in member accounts, the WorkSpaces administrator principal needs these permissions, and no service control policy can block them:
sso:DescribeInstance,sso:CreateApplication,sso:PutApplicationGrant,sso:PutApplicationAuthenticationMethod,sso:DeleteApplication,sso:DescribeApplicationandsso:GetApplicationGrant.
Step 2: Set up the multi-Region KMS key before you replicate
Identity Center uses AWS-owned keys by default, and replication needs a customer-managed multi-Region key instead. In the AWS KMS console, in the same Region as your Identity Center instance, create a Symmetric key with Encrypt and decrypt usage and Multi-Region key regionality.
The blog is firm on this point: a single-Region key cannot be converted later. If you pick the wrong type, you have to create a new key and reconfigure Identity Center.
The key policy needs at least the baseline statements AWS describes for Identity Center administrators, the Identity Center and Identity Store services, and AWS managed applications and their administrators. Then associate the key with Identity Center under Settings → Management → Manage encryption.
Replicate the key from the KMS console's Regionality tab with Create new replica keys, choosing each target Region. AWS's GA announcement makes the order explicit: you must first replicate the customer managed AWS KMS key to that Region and configure the replica key with the permissions required for IAM Identity Center operations.
Watch out: changes to a KMS key policy do not copy to the replicas. If you edit the policy in one Region, you have to make the same change in every other Region yourself.
Step 3: Turn on Identity Center replication
From the primary Region's Identity Center console, open Settings and add each target Region. The blog's example Regions are eu-central-1 and ap-south-1.
The menu label differs between sources. The walkthrough says to use a Region replication section. AWS's GA announcement says to choose Settings in the left-navigation pane, and select the Management tab, then choose Add Region. Either way, you're looking for Add Region.
Then check each target Region. The replica should be active and show the same users and groups as the primary. Record each Region's Instance ARN.
There's an Entra step the blog doesn't mention. An independent write-up of the feature notes that you'll need to add the new Region's ACS URL to your external IdP configuration so users get redirected correctly. AWS's own documentation also requires the external IdP to support multiple SAML ACS URLs for full multi-Region support. Microsoft Entra ID is on its list of IdPs that do. If sign-in works in the primary Region but fails in a replica Region, check the Reply URL entries on the Entra enterprise app first.
Step 4: Set up the Entra app registration and Autopilot
You need one single-tenant app registration, shared by every Region. In the Entra admin center, choose App registrations → New registration. Give it a name such as AWS-WorkSpaces-Autopilot and select Accounts in this organizational directory only. Then add these Microsoft Graph application permissions:
| Permission | Purpose |
|---|---|
| DeviceManagementServiceConfig.ReadWrite.All | Register and remove devices in Autopilot |
| Device.ReadWrite.All | Manage device objects in Entra ID |
| DeviceManagementManagedDevices.ReadWrite.All | Manage Intune-enrolled devices |
The WorkSpaces Administration Guide explains which permission does what. Only DeviceManagementServiceConfig.ReadWrite.All is needed to create an Entra-joined WorkSpace. The other two are used when you terminate or rebuild one. Without them, terminated WorkSpaces stay in Intune and Entra until you remove them yourself.
So granting fewer permissions isn't free: you trade lower privilege for manual cleanup of stale device objects. Grant admin consent, create a client secret, copy the secret value straight away, and record the Application (client) ID.
In the Intune admin center, create one Security group with Dynamic Device membership per Region, with a rule like this:
(device.devicePhysicalIds -any (_ -eq "[OrderID]:WorkSpaces-USEast1"))
There's a formatting difference to know about. The blog post shows the token with double square brackets. AWS's WorkSpaces Administration Guide and the standard Autopilot group-tag syntax use single brackets, as shown above. Use the guide's format.
The value after the colon must exactly match the WorkSpaces directory name you'll create in Step 6. WorkSpaces uses the directory name as the Autopilot group tag, and the group tag maps to the OrderID attribute on Entra devices.
To finish the Autopilot setup:
- Turn on automatic MDM enrollment under Devices → Windows → Enrollment → Automatic Enrollment, with the MDM user scope set to All or to a group containing your WorkSpaces users.
- Create a Windows PC Autopilot deployment profile per Region, with User-driven deployment mode and Microsoft Entra joined selected.
- Assign each profile to its regional device group.
The admin guide also mentions an optional device-name template if you want consistent computer names.
Step 5: Store the credentials in Secrets Manager in each Region
This step uses a second multi-Region KMS key, separate from the Identity Center key, and it encrypts only the stored credentials. The AWS guide warns against encrypting the secret with the default key, because the WorkSpaces service can't access it. The key policy must grant kms:Decrypt and kms:DescribeKey to the workspaces.amazonaws.com service principal. The blog also suggests testing the key with a test directory and WorkSpace before you replicate it.
Create an Other type of secret with two key/value pairs: application_id and application_password. Add a resource policy that grants secretsmanager:GetSecretValue to workspaces.amazonaws.com. Then use Replicate secret to other Regions, choosing the local replica key in each Region.
Step 6: Create a directory and launch WorkSpaces in each Region
In each Region, choose Directories → Create directory in the WorkSpaces console and set:
- WorkSpaces type: Personal
- WorkSpace device management: Microsoft Entra ID
- Microsoft Entra tenant ID: your tenant ID
- Entra ID application credentials: the regional secret from Step 5
- User identity source: the local Identity Center replica, not the primary
- Directory name: an exact match for the regional Autopilot OrderID
- Networking: a VPC and two subnets in different Availability Zones, both with outbound internet access
Check for one setting the blog doesn't cover. The admin guide says you must select Enable dedicated WorkSpace under Configuration to launch BYOL desktops. If that option is missing, BYOL hasn't been enabled on your account.
Several choices are permanent once the directory exists. You can't change the tenant ID, the attached secret, the associated Identity Center instance or the directory name. You can update what's stored in the secret. If you pick the primary instance in Step 6 when you meant the replica, the guide's cross-Region note applies: you may see higher latency during provisioning and login, and the extra delay grows with the distance between Regions.
After the directory shows Active, confirm that it references the local replica and that an Identity Center application ARN has been created. Then launch WorkSpaces from a BYOL Windows 10/11 bundle for users synced from Entra.
What success looks like:
- Each device appears in Intune under Devices → Windows.
- In the Entra admin center, each device shows as Microsoft Entra joined and belongs to the correct regional Autopilot group.
- A user enters the registration code in the WorkSpaces client, is redirected to Entra through the local replica's SAML federation, and reaches their desktop.
Repeat the check in every Region.
Where "regional independence" stops
AWS's blog describes an outage in one Region as leaving the others unaffected. That's true for sign-in, with conditions:
- Most administration happens in the primary Region. AWS's resiliency documentation says Identity Center supports most administrative functions only from the primary Region, including the external IdP connection and user and group sync. If the primary Region goes down, existing users can keep signing in, but identity changes stop propagating until it recovers. Joiners, leavers and group changes wait.
- Entra is a separate dependency. Replication protects against an AWS Region failure, not an Entra outage. AWS recommends break-glass access for a small group of privileged administrators during an external IdP disruption, and notes that emergency access using external IdP identities doesn't protect against that disruption.
- Secrets expire. The Entra client secret has an expiry date. When you rotate it, you have to update the secret in every Region. Secrets Manager automatic rotation can help.
Operations and cleanup
For day-to-day running, the blog recommends:
- Region-aware directory names such as
WorkSpaces-<RegionCode> - Watching SCIM health in the Entra provisioning logs
- CloudWatch alarms for replication lag
- CloudFormation StackSets or Terraform to set up new Regions
Rotating a multi-Region key rotates its key material in all Regions, and key usage is logged in CloudTrail.
To tear down, work in this order:
- Terminate WorkSpaces.
- Delete the directories.
- Delete the secrets.
- Schedule deletion of the Secrets Manager KMS keys. There's a minimum seven-day waiting period.
- Remove Identity Center replication for Regions you no longer need.
- Delete the Intune device groups and Autopilot profiles.
- Delete the Entra app registration if nothing else uses it.
The bottom line: for organizations already using Entra and Intune for Windows management, this is a clean way to run Windows desktops on AWS in several Regions without one Region being a single point of failure for sign-in. Most failures will come from small details: a mismatched OrderID, a single-Region key, a missing ACS URL, or a secret that expired without anyone noticing. Run the per-Region tests the walkthrough recommends rather than relying on a green status in the console.
References
- Deploy Amazon WorkSpaces across Regions with Entra ID and IAM Identity Center - Amazon Web Services (AWS) Amazon Web Services (AWS) · 2026-10-23T14:26:01+00:00
- Setup AWS IAM Identity Center with Multi-Region replication medium.com
- AWS News Blog aws.amazon.com