Skip to content
TheChatArchiveThe Chat Archive
Geminigemini-2.5-pro-preview-05-06· GoogleHugging Face LMArena Human Preference 140K

Is there a minimum limit for users in a tenant to be egligeble for Advanced data…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Googlegemma-3-27b-it’s answer.
  1. User

    Is there a minimum limit for users in a tenant to be egligeble for Advanced data residency?

  2. Gemini Assistant

    No, there is no specific minimum number of users required for the Advanced Data Residency (ADR) add-on itself.

    You can purchase and assign ADR licenses for as few as one user, provided your tenant meets the other prerequisites.

    Here's a breakdown:

    1. ADR is an Add-on: Advanced Data Residency is an add-on license that you purchase for specific users who require their data to be stored in a particular local datacenter region within their existing Microsoft 365 geography.
    2. No User Minimum for the Add-on: Unlike the standard Multi-Geo capabilities (which do have minimum seat requirements, often 250 or 500 paid seats), the ADR add-on can be applied on a per-user basis. If you have only one user who needs it, you can purchase one ADR license for that user.
    3. Tenant Prerequisites Still Apply:
      • Your tenant must have a qualifying underlying Microsoft 365 subscription (e.g., Microsoft 365 F1, F3, E3, E5, A1, A3, A5; Office 365 F3, E1, E3, E5, A1, A3, A5; Exchange Online Plan 1 or 2; SharePoint Online Plan 1 or 2; OneDrive for Business Plan 1 or 2).
      • Your tenant's primary data location (as determined during initial setup) must be in an eligible "Geography" that supports ADR.
      • You need to purchase the Advanced Data Residency add-on SKU.

    In summary, while your overall tenant needs to be eligible (e.g., have a paid subscription and be in a supported geography), you can then apply the ADR add-on to any number of users, from one to all of them, without a specific minimum count for the ADR licenses themselves.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.