Get-MgAllSite returns DataLocationCode as null/empty in SiteCollection

[m-balous]

Describe the bug

When using Get-MgAllSite with -Property siteCollection, the returned MicrosoftGraphSiteCollection object has DataLocationCode always null/empty, even though the property exists on the model, the tenant is multi geo and the site is in another region.

  Actual output:

   ArchivalDetails      : Microsoft.Graph.PowerShell.Models.MicrosoftGraphSiteArchivalDetails
   DataLocationCode     :
   Hostname             : contoso.sharepoint.com
   Root                 : Microsoft.Graph.PowerShell.Models.MicrosoftGraphRoot
   AdditionalProperties : {}

Expected behavior

DataLocationCode should contain the geo location code (e.g. NAM, EUR).

How to reproduce

Replace contoso.onmicrosoft.com with multi geo tenant and ensure you have sites in multiple regions.

# Module version: 2.35.1
Connect-MgGraph -TenantId "contoso.onmicrosoft.com" -ClientSecretCredential $cred -NoWelcome

$sites = Get-MgAllSite -Top 1 -Property siteCollection
$sites[0].SiteCollection | Format-List *

Reproduce via: Get-AllSites_graph.ps1.txt

SDK Version

No response

Latest version known to work for scenario above?

2.35.1

Known Workarounds

No response

Debug output

Click to expand log

```

</details>


### Configuration

- OS: Windows 11 x64

### Other information

It looks like this could be related to https://github.com/OneDrive/onedrive-api-docs/issues/1091

[lramosvea]

@m-balous could you please share the -debug output?

[m-balous]

Sure. Though nothing interesting is going on there:

   DEBUG: [CmdletBeginProcessing]: - Get-MgAllSite begin processing with parameterSet 'Get2'.
   DEBUG: ClientSecretCredential.GetToken invoked. Scopes: [ https://graph.microsoft.com/.default ] ParentRequestId:
   DEBUG: False MSAL 4.78.0.0 MSAL.CoreCLR .NET 9.0.10 Microsoft Windows 10.0.26200 === Token Acquisition (ClientCredentialRequest) started: Scopes: https://graph.microsoft.com/.default Authority Host: login.microsoftonline.com
   DEBUG: Request [a288167e-...] GET https://login.microsoftonline.com/common/discovery/instance?api-version=1.1&authorization_endpoint=REDACTED
   DEBUG: Response [a288167e-...] 200 OK (00.1s)
   DEBUG: Request [c8b27075-...] POST https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token
   DEBUG: Response [c8b27075-...] 200 OK (01.0s)
   DEBUG: === Token Acquisition finished successfully:
   DEBUG: AT expiration time: 20.02.2026 20:52:35 +00:00, scopes: https://graph.microsoft.com/.default. source: IdentityProvider
   DEBUG: ClientSecretCredential.GetToken succeeded. Scopes: [ https://graph.microsoft.com/.default ]

The Graph API itself seems to have the same problem.

[gavinbarron]

That doesn't have the output from the request to /sites which it the part we're interested in in this case, that's just the token acquisition steps.

When you say the Graph API itself has the same problem, that's unsurprising, these cmdlets are wrappers for ease of use from PowerShell. They simply call the same http endpoints that exist in Microsoft Graph.

Looking at the documentation for the siteCollection type I see this note that might be relevant:

dataLocationCode | string | The geographic region code for where this site collection resides. Only present for multi-geo tenants. Read-only. -- | -- | --

Are you using a multi-geo tenant?

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.