Yardi Virtuoso (Preview)

Yardi Virtuoso provides secure, real-time access to Yardi data and tools through Co-Pilot. It enables investment, property and asset management professionals to query financial models, predictive maintenance insights, market analysis, and portfolio data using natural language. Users can ask complex operational questions, explore strategic scenarios, and perform analysis without manual data extraction, all grounded in accurate, enterprise-grade Yardi data.

This connector is available in the following products and regions:

Yardi Virtuoso Connector

Yardi Virtuoso provides secure, real-time access to Yardi data and tools through Microsoft Copilot. It enables investment, property and asset management professionals to query financial models, predictive maintenance insights, market analysis, and portfolio data using natural language. Users can ask complex operational questions, explore strategic scenarios, and perform analysis without manual data extraction, all grounded in accurate, enterprise-grade Yardi data.

The connector is an implementation of the Model Context Protocol (MCP), an open standard for connecting AI assistants to external systems such as business tools, data repositories, and development environments. Rather than exposing a fixed set of REST operations, the connector speaks MCP over streamable HTTP, so the Yardi Virtuoso MCP server advertises its own tools and resources to the calling agent at runtime. This means new Yardi capabilities become available to agents without republishing the connector.

Prerequisites

You will need the following to proceed:

• A Microsoft Power Apps or Power Automate plan with the custom connector feature
• A Microsoft Copilot Studio license, for agents that consume the MCP server
• A licensed Yardi Virtuoso subscription
• A YardiOne account with access to the Yardi data and tools you intend to query
• The Power Platform CLI tools (paconn), if you are deploying from source rather than importing the managed solution

Building the connector

The Yardi Virtuoso MCP server is secured by YardiOne, which acts as the OAuth 2.0 authorization server. Authentication uses OAuth 2.0 with PKCE and Protected Resource Metadata (oauth2pkcewithprm), so the connector discovers the authorization server and registers itself dynamically instead of relying on a pre-provisioned client ID and secret.

Because of that discovery flow, there is no Entra ID app registration step and no client secret to manage. The connector declares the MCP server address and Power Platform handles the rest of the handshake:

1. The connector advertises its protected resource, https://mcp.virtuoso.ai/mcp, through the ServerUrl connection parameter.
2. On first connection, Power Platform fetches the protected resource metadata from the MCP server, which points at the YardiOne authorization server.
3. The connector registers dynamically with YardiOne and redirects the user to sign in.
4. YardiOne issues an access token scoped to that user, and the connector attaches it as a bearer token on every MCP request.

Access is therefore evaluated per user against their YardiOne entitlements. An agent can only reach the Yardi data and tools that the signed-in user is already permitted to see, and every tool invocation is auditable back to that identity.

The redirect URL configured for this connector is:

https://global.consent.azure-apim.net/redirect/cre88-5fvirt-5fprod-5fdyn-5foauth-5fdisc-5f985796682d33968b

This is a GlobalPerConnector redirect, so it is specific to this connector registration and must be allow-listed by the YardiOne authorization server.

Deploying the connector

Import the managed solution included in this package:

pac solution import --path YardiVirtuosoConnector_1_0_0_2_managed.zip

The solution packages the custom connector component only. It contains no additional tables, workflows, or security roles.

Alternatively, to deploy from the connector definition in this repository:

paconn create --api-def apiDefinition.swagger.json --api-prop apiProperties.json

Supported Operations

The connector exposes a single Power Platform operation, which carries the MCP protocol:

• Yardi Virtuoso (InvokeServer): Invokes the Yardi Virtuoso MCP server over streamable HTTP. This is the transport for all MCP traffic, including tool discovery and tool invocation.

Agents do not call that operation directly. Once a connection is authorized, Copilot Studio issues an MCP tools/list request and the Yardi Virtuoso server returns the tools available to the signed-in user. The agent then invokes those tools by name. Because the tool catalog is served by Yardi Virtuoso rather than declared in the connector's OpenAPI definition, it can change on the server side without a connector update.

Known Issues and Limitations

• The connector uses the mcp-streamable-1.0 agentic protocol and is intended for use in Microsoft Copilot Studio agents. It is not designed for use as a conventional action in Power Automate flows or Power Apps.
• The tool catalog is resolved at runtime from the Yardi Virtuoso MCP server, so the operations available to an agent depend on the server version and on the signed-in user's YardiOne entitlements.
• Each connection is bound to an individual YardiOne user. On-behalf-of login is not supported, so connections cannot be shared across users.
• Outbound access to mcp.virtuoso.ai over HTTPS is required. Environments that restrict egress must allow the Azure service tags used by Power Platform in the relevant region.

Actions

Yardi Virtuoso