--- title: How to use Get-ResourceConfig in Powershell slug: get-resourceconfig-powershell published: 2025-09-22T23:02:34.000Z updated: 2025-09-22T23:02:34.000Z feature_image: /blog/images/get-resourceconfig-powershell/get-resourceconfig-syntax-microsoft-learn.1600.webp feature_image_alt: Microsoft Learn documentation for the Get-ResourceConfig cmdlet showing its PowerShell syntax author: James Futhey author_slug: james meta_description: Learn how to use the Get-ResourceConfig PowerShell cmdlet to manage and view Exchange resource property schemas for mailboxes and rooms. status: published --- In Exchange, managing **resource mailboxes** like conference rooms or equipment is a common task for administrators. These mailboxes often need additional **configuration** for scheduling, resource types, and booking rules. The **Get-ResourceConfig** cmdlet in PowerShell helps administrators view the **resource property schema** that underpins how resources are defined and managed in an Exchange organization. ## What is the Get-ResourceConfig Cmdlet? The **Get-ResourceConfig** cmdlet retrieves the resource property schema defined in Exchange. This schema includes **resource types, resource properties**, and other elements that determine how **room and equipment mailboxes** can be configured and used. Administrators typically use it in combination with **Set-ResourceConfig** to modify or update the schema as their organization’s needs evolve. This cmdlet is useful when working with **Exchange Server** or **Exchange Online** environments where conference rooms, projectors, and equipment mailboxes must follow consistent booking rules and **capabilities**. ### Syntax Get-ResourceConfig [[-Identity] <OrganizationIdParameter>] ```powershell [-DomainController ] [] ``` ### Parameters - **\-DomainController** - Specifies the domain controller FQDN to use for reading or writing Active Directory data. _Applicable only in on-premises Exchange._ Type: Fqdn. - **\-Identity** - Organization identifier parameter (type: OrganizationIdParameter). **Reserved for internal Microsoft use** and available only in on-premises Exchange. Use is normally not required for standard admin queries. - **CommonParameters** - The usual PowerShell common parameters are supported (for example **\-Debug, \-ErrorAction, \-Verbose, \-OutVariable**, etc.). ## Practical Uses The **Get-ResourceConfig** cmdlet has a focused role: it shows you the resource property schema that your organization has defined for room and equipment mailboxes. While it’s not a cmdlet you’ll run every day, it becomes important in specific administrative and operational scenarios. ### 1\. Validating resource schema before assigning properties Before assigning custom properties such as **Room/Video Conferencing** or **Equipment/Projector** to a mailbox, system admins often need to confirm what is currently defined in the organization’s schema. Running **Get-ResourceConfig**provides a clear picture of which resource types and custom attributes exist, ensuring that admins don’t assign values that aren’t recognized. This prevents **validation** errors when applying properties with **Set-Mailbox**. ### 2\. Auditing resource properties across an Exchange environment Organizations that rely heavily on **room mailboxes** and **equipment mailboxes** often need consistency. For example, a company might want all conference rooms to be labeled with **capacity** and **capabilities** (such as a smartboard or TV screen). **Get-ResourceConfig** helps admins confirm that the **resourceKeys** in the schema are aligned with corporate standards. During an audit, this makes it easier to catch missing or outdated attributes before they affect room booking or user experience in **Teams** and **Outlook**. ### 3\. Troubleshooting booking issues with meeting resources If end users report problems such as missing attributes in a room finder tool or unexpected behavior in resource **booking** workflows, admins can use **Get-ResourceConfig** to check whether the expected **configuration** is present in the resource schema. This helps determine if the issue is caused by a misapplied mailbox setting (**Set-Mailbox**) or if the schema itself is incomplete and needs modification through **Set-ResourceConfig**. ## Prerequisites - You need to be assigned **permissions** (via RBAC) that allow you to run the **Get-ResourceConfig** cmdlet. If your role does not include the relevant management role(s), some parameters or parts of the output may be unavailable. - The cmdlet is available in **Exchange Server 2010, 2013, 2016, 2019**, and in Exchange Online. - If using **\-DomainController** parameter, it is applicable **only in on-premises Exchange**. That parameter does _not_ apply in Exchange Online. ## How to Use Get-ResourceConfig: X Examples Below are the most common and practical ways to use **Get-ResourceConfig** in Exchange Server and Exchange Online environments. These examples walk through real scenarios where an admin needs to query the resource schema. ### 1\. View the full resource property schema for the organization When you want to see all the custom resource properties that are currently available across the organization, running [**Get-ResourceConfig**](https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/get-resourceconfig?view=exchange-ps) without parameters returns the complete schema. This shows properties like **Room/Video Conferencing, Room/Whiteboard**, or **Equipment/Projector** if they’ve been defined using **Set-ResourceConfig. Command:** `Get-ResourceConfig` **What it does:** The output reveals the list of **resource property schema entries**, including the names, resource types, and keys available. This is often the starting point before applying custom resource properties to mailboxes with **Set-Mailbox**. ### 2\. Query using the Identity parameter The **\-Identity** parameter is used mainly in **on-premises Exchange** and is reserved for internal Microsoft scenarios. However, if you provide an **organization identifier**, the command narrows the schema output to that scope. **Command:** ```powershell Get-ResourceConfig -Identity "Contoso" ``` **What it does:** Retrieves the resource configuration schema tied specifically to the organization ID "Contoso". While most admins won’t use this daily, it’s important in multi-tenant or delegated setups. ### 3\. Use DomainController to query directly from AD (on-premises only) When working in **on-premises Exchange**, you can target a specific domain controller with the **\-DomainController**parameter. **Command:** ```powershell Get-ResourceConfig -DomainController dc01.contoso.com ``` **What it does:** Forces the command to read the schema directly from the **specified domain controller (FQDN)** instead of relying on the default topology service. Useful if you suspect replication delays or need the most current values. ### 4\. Compare schema outputs across domain controllers (on-premises only) In large on-premises environments, replication delays can cause discrepancies between domain controllers. You can explicitly query multiple DCs to ensure the schema is consistent. **Command:** ```powershell Get-ResourceConfig -DomainController dc01.contoso.com ``` ```powershell Get-ResourceConfig -DomainController dc02.contoso.com ``` **What it does:** Retrieves the resource schema from each specified domain controller. If the outputs differ, admins know replication hasn’t completed, which could explain missing or inconsistent properties on certain room or equipment mailboxes. ## Final note **Get-ResourceConfig** is a focused, read-only cmdlet that exposes the organization’s **custom room and equipment mailbox schema**. While it has very few parameters, it is a critical tool for **Exchange administrators** who need to validate, audit, or troubleshoot **resource properties** before applying them with **Set-Mailbox** or managing them with **Set-ResourceConfig**.For administrators, the key takeaway is: **always check the schema after changes, confirm consistency across domain controllers (on-premises), and use it to validate resource assignments**. Despite its simplicity, it plays an important role in maintaining accurate and functional resource mailboxes in Exchange.