Yeeflow Studio brings application-building guidance and an authenticated Yeeflow connection to Microsoft 365 Copilot. Use it to turn requirements into plans for forms, data lists, workflows, dashboards, reports and custom code. Review generated artifacts and confirm the exact target before a live change.

This guide covers getting started with the Marketplace version in Copilot Cowork. Microsoft interface labels and availability can vary by tenant and host. Yeeflow Studio is different from the existing Yeeflow app for Microsoft Teams and from a Copilot built inside a Yeeflow application.

Scope of this guide: Follow the setup checks below in your current host. Labels, navigation, registration and consent screens may vary by host or version. Images are labeled as actual screenshots or instructional illustrations. Existing-session screenshots do not reproduce a first installation or first sign-in. A separate captured application-review rehearsal is described below.

If Cowork is unavailable, ask your Microsoft 365 administrator to check your access and applicable billing policy. See Microsoft's current Cowork access guidance.

Use the same intended work or school account throughout setup. Choose the entry path that matches your screen, then follow the shared installation and connection steps below.

Open Copilot from the Teams app rail. Expand the Copilot navigation and select Plugins. In the plugin management area, choose Cowork. If Yeeflow Studio is already listed, open it; otherwise continue to Step 1 to find and add it. The screenshot shows an existing installed plugin, not a new installation.

Copilot in Microsoft Teams: Plugins → Cowork, with Yeeflow Studio shown under Added.

Open Microsoft 365 Copilot in your browser and select Plugins. Search for Yeeflow Studio. Microsoft may show this area under Customize → Plugins; follow the labels in your current host.

Web Copilot: Plugins → Cowork, with a search for Yeeflow Studio showing the already-added plugin. Added counts are account-specific.

Both paths continue here: identify the official plugin, add it if necessary, then connect your Yeeflow account.

Installation overview, not a product screenshot. Add or Install is needed only when Studio is not already present.

Check installation: Return to the plugin management area and look for Yeeflow Studio in your installed or added plugins. Microsoft documents an Installed section; labels may differ. Refresh the list once if necessary before retrying the acquisition action. Do not repeatedly select Add or Install.

Microsoft's Cowork documentation may describe plugin discovery under Customize → Plugins, or through a plus menu. Use the labels shown in your current host rather than assuming every Microsoft interface is identical.

If the plugin is missing or unavailable, contact your Microsoft 365 administrator rather than uploading an unverified package. See Microsoft's plugin management instructions.

Open Yeeflow Studio in the plugin management area. Enable it for the conversation if it is off, then check its Yeeflow connection status. Your host may show an Enable Yeeflow Studio control; navigation and labels can vary by host or version.

Actual plugin details. This example is already Connected; a new account can show Connect Yeeflow instead.

If the connection is not connected, select its connection action, which may be labeled Connect Yeeflow, and follow the sign-in link. Check that the page belongs to Yeeflow before continuing. If the destination is unexpected, stop and ask your administrator.

Sign in with the intended Yeeflow account using your established sign-in method. If a Create your account page appears, check that the email matches the account your administrator intended you to use, review the terms and privacy policy, and complete registration only if needed. If you already have a Yeeflow account, resolve any identity mismatch with your administrator before creating another. Registration screens can vary by host or version. Do not put passwords, tokens or API keys in the conversation.

Instructional process diagram, not a screenshot. Sign-in and registration screens can differ by account and host.

Review the actual Yeeflow authorization request and its requested scopes. Consent titles and scope wording may vary by host or version. If the title mentions Microsoft Teams MCP, that name alone does not prove the request is legitimate. Continue only from the official Studio plugin and only if your organization authorizes the connection. If an Offline Access scope appears, do not interpret it as a promise that Studio works without an internet connection. Ask your administrator if the request or revocation options are unclear.

Illustration based on an observed consent request. The account name is fictional; review your actual request and your organization’s approval.

Return to Copilot and check for Yeeflow: Connected in the plugin connection details. Keep Yeeflow Studio enabled. If the status is different, follow the message shown or ask your administrator. Connected confirms authentication, not permission to access every workspace or application.

Example connection screen showing Connected. Live actions still follow the signed-in user’s Yeeflow permissions.

Follow the plugin's own connection flow before adding a separate manual MCP connection. An existing manual connection is not proof that the Marketplace plugin is connected. Microsoft's plugin connection guidance explains service sign-in.

Begin with a read-only request:

Use Yeeflow Studio to show which Yeeflow account I am connected as. Do not change any data.

Check that the response actually identifies the intended account before continuing. If the plugin cannot perform a requested check, stop and report that limitation rather than assuming success. Then ask:

List the Yeeflow workspaces I can access. Do not create or update anything.

Select your intended workspace by its exact name. Do not assume that an example workspace named Demo exists in your organization. If you cannot see a resource you expect, ask your Yeeflow administrator to check your access.

Application builders with suitable access can start by understanding an existing application's structure:

In [workspace name], review the configuration of [application name]. Summarize its data lists, forms and workflows. Read configuration only; do not read business records, run workflows or make changes. Tell me which parts you actually inspected.

Example: in an internal test in Microsoft Copilot Cowork on 8 November 2026 (SGT), Studio returned a configuration-review response for an IT equipment application and separated an existing inventory calculation from a proposed alert change. This was a single-account test, not a full business-process or permissions test.

Actual single-account configuration review. Existing calculations and proposed changes are separated; no workflow was executed.

Review the displayed tool activity and compare important details with the application in Yeeflow. A fluent explanation alone is not evidence that an operation ran successfully.

These are starting prompts, not guarantees that every action is available in your account. This guide doesn't confirm runtime operations through Yeeflow Studio, such as reading or updating business records or approving tasks, and Studio's exact list of tools isn't documented here. Don't rely on them until you have confirmed them in your environment. This doesn't mean those operations are unavailable; check with Yeeflow support for your scenario. Before a live change, review generated artifacts, confirm the exact target and intended change, then check the resulting state in Yeeflow. Test new applications and workflows in an appropriate non-production environment before business use.

According to the Marketplace listing, some workflows require files supplied in the task or an available browser, and the plugin reports when a required capability is unavailable. Supply the required files or supported browser capability. If something is unavailable, ask for an explicit blocked or not-completed report; do not infer completion from a fluent answer.

Related article: Yeeflow Studio in Microsoft Copilot: FAQ and troubleshooting