Use these checks when installing or using the Marketplace version of Yeeflow Studio in Microsoft Copilot. Interface labels can differ between the web experience, Teams and your organization's deployment.

Yeeflow Studio brings application-building guidance and an authenticated Yeeflow connection to Microsoft 365 Copilot. Use it to plan, build and review Yeeflow applications: 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.

No. The Yeeflow Studio Marketplace offer is a Copilot plugin experience. The existing Yeeflow Teams app and a Copilot created inside a Yeeflow application are separate experiences. Check the product name and publisher before following an installation guide.

Yes. You need an active Yeeflow account with access to the target workspace and application. Live actions follow the signed-in user’s Yeeflow permissions; connecting does not grant additional access. See the Yeeflow connection guide.

Do not assume so. The listing requires an eligible Microsoft 365 Copilot environment. Yeeflow access and Microsoft licensing are managed separately, and Additional purchase may be required. Ask your administrator to check your environment and the current Cowork access controls. This article does not establish a total cost.

Check that you are signed in to the intended work or school account and organization. Look for the official Yeeflow Studio listing, published by YEEFLOW SINGAPORE PTE LTD. If it is unavailable in your account, ask your Microsoft 365 administrator to check plugin availability. Do not work around an organizational restriction by uploading another package.

Connected describes the service connection, not permission to every resource. Ask Studio to identify the connected Yeeflow account and list available workspaces, if those checks are available in your host. Do not infer success if a check is unavailable. Verify the exact workspace and application. Your Yeeflow administrator may need to review access. Do not create a duplicate organization just to resolve missing access.

You may have a Marketplace version and a separately uploaded or shared test package. Compare their publisher and management details rather than choosing by name alone. Ask the package owner or administrator to identify the correct version. Do not delete a shared package without checking who depends on it.

Compare the plugin list in a fresh web Copilot session using the same Microsoft account and organization. Then reopen Copilot in a new Teams window or refresh the client. Differences between views do not by themselves establish a cache problem. If the entry remains in fresh views, ask your administrator or Microsoft support to inspect the deployment state.

No. Microsoft documents that disabling a plugin hides its skills and connectors from conversations until it is enabled again; it can remain in the management list. Removal affects future conversations, while active conversations already using the plugin may continue until they end. Only an administrator can remove an admin-deployed plugin. Follow Microsoft’s current plugin guidance; do not use organization-wide blocking as a substitute for a personal display preference.

Start with the connection included in the plugin. Avoid adding a duplicate manual connection unless your documented setup requires it. A separate MCP connection and Studio can appear together; verify which connection the conversation is using and which account it represents.

Review the generated artifacts and confirm the exact target and intended application change before a live action. Afterward, check the resulting state and functionally test the affected application. A plan, an explanation and a completed action are different states. 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.

Do not assume these follow from installing Studio. They depend on other Microsoft capabilities, available connections, licensing, permissions and the specific workflow. Validate the complete scenario before relying on it or describing it as supported.

Include the host you used, approximate time and timezone, plugin version, exact error text, whether connection identity was correct and whether the issue also occurs in a fresh web session. Use a redacted screenshot where helpful. Never send passwords, access tokens, cookies, private keys or unnecessary business-record content.

If a Create your account page appears, check that the email matches the address your administrator intended you to use. Review the terms and privacy policy and complete personal registration only if needed. If you already use Yeeflow with another sign-in method or email, check with your administrator before creating another account. Registration screens may vary by host or version.

Consent titles and requested scope wording may vary by host or version. If a consent page mentions Microsoft Teams MCP, that client name alone is not proof that the page is legitimate. Start from the official Studio plugin and check the Yeeflow sign-in destination before continuing. Review the actual requested permissions and your organization’s approval. If Offline Access appears, do not interpret it as a promise that Studio works without an internet connection. If the request or revocation options are unclear, stop and ask your administrator.

Check whether Yeeflow Studio is enabled in your plugin management area. Your host may show an Enable Yeeflow Studio control. Labels and connection-button behavior can vary by host or version; check the current status after enabling it. If the connection action stays unavailable, ask your administrator to check your account’s Copilot access and plugin availability.

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 a prerequisite is unavailable, request an explicit blocked or not-completed report rather than assuming a fluent answer means the work completed.

This FAQ doesn't confirm Studio's exact list of tools, availability across regions or sovereign clouds, total cost, or Microsoft's data-retention arrangements. Check current Yeeflow and Microsoft documentation and confirm the requirements for your environment before relying on these points. Information about other connectors or where Yeeflow is hosted doesn't answer these questions about Studio.

Related article: Install and get started with Yeeflow Studio in Microsoft Copilot