How do I download the source code of a model driven power app in Teams environment?

To download the source code of a model-driven Power App in a Teams environment, you will need to export the app as a solution. Here are the steps you can follow:

1. Open Power Apps: Sign in to the Power Apps portal.
2. Select Solutions: On the left navigation pane, select Solutions. If you don't see it, click on More to find it.
3. Open the Solution: Find and open the solution that contains your model-driven app.
4. Export the Solution: On the toolbar, select Export. Before exporting, it is recommended to Publish all changes and Check for issues.
5. Export Options: In the export dialog, you can accept the default incremented version number or enter a new one. Choose whether to export as Managed or Unmanaged and then select Export.
6. Download the Zip File: Once the export is complete, a .zip package file containing your app and its components will be downloaded to your default downloads folder.

This .zip file can then be used for documentation or imported into another environment as needed.

Note: The app URL is not exported when using this method, so you may need to document that separately if necessary.

Hi @Brenda Hogenkamp,
Thank you for posting your question to Microsoft Q&A Forum.

You can’t download “source code” for a Model‑Driven App but you can export it as a Solution

Model‑driven Power Apps don’t produce traditional source code like canvas apps or custom code projects. Instead, everything is stored as metadata in Microsoft Dataverse.
To document or move your app, the correct method is to package it into a Solution and export that solution.

This applies even when the app was built inside Microsoft Teams. Teams-hosted model‑driven apps still run on Dataverse and are packaged through the Power Apps Maker portal.

The official method is to add your app to a Solution and then export that solution as a .zip file.
That .zip is the transportable, inspectable representation of your app’s configuration.

Microsoft’s documentation explains it clearly:
Model‑driven apps are distributed as solution components, and exporting the solution packages the app and its components into a .zip file.
You can find more information about this via this document: Distribute a model-driven app using a solution

1. Go to Power Apps Maker Portal
   https://make.powerapps.com
2. Select your environment
   Ensure you’re in the environment where your Teams‑based Dataverse instance resides.
3. Create a new Solution
   • Left navigation → Solutions → New solution
   • Provide name, publisher, and version → Save
   • 
4. Add your model‑driven app
   • Open the solution
   • Select Add Existing → App → Model‑driven app
   • Choose your app → Add
5. Allow Power Apps to bring in required components
   If prompted, choose Yes, include required components.
   This ensures all tables, forms, views, and site maps are included.
6. Export the solution
   • Open your solution → Export
   • Publish changes and run solution checker
   • Choose Managed or Unmanaged
   • Click Export
   • Download the resulting .zip file (your app package).
     This .zip contains your “metadata source,” which can be unpacked for documentation. For more information, please visist: Export solution

There is two export types you can choose:

• Unmanaged = Best for documentation, reviewing metadata, and version control.
• Managed = Best for distributing to other environments but not for editing.
• For more information, please go to: Solutions in Power Apps overview

Unmanaged versions are generally considered the source for Power Platform assets and should be checked into source control.

Even though you built your app inside Power Apps for Teams, a model‑driven app still requires Dataverse and follows full solution‑based ALM.
This means you can export it exactly the same way as any Dataverse app.

Furthermore, to ensure you receive the most accurate and expert guidance, if you have any questions about Power Automate process, I recommend posting your query on the Find Answers | Microsoft Power Platform Community

The Power Platform Community is an excellent resource supported by knowledgeable members, including Microsoft experts and partners. By posting your question there, you’ll gain access to specialized insights and solutions tailored to Power Platform, ensuring your issue is resolved effectively.

We recommend this approach because our internal resources for Power Platform are limited, and we want to make sure you receive accurate, comprehensive guidance. The community is the best place for targeted help and also provides an opportunity for others to learn from your experience.

Note: Thank you for understanding the scope of support available in this forum. Our primary goal is to guide users to the most appropriate resources for accurate and timely assistance. Since this category focuses on Microsoft 365-related concerns, expertise on Power Automate is limited here. To ensure you receive the best possible help quickly, we’re directing you to the Power Platform Community, where specialists and experienced members can provide targeted solutions.

I hope the information provided proves useful. Please proceed with the outlined steps and let me know whether they resolve the issue. If not, I’ll be glad to continue working with you to find a solution.

Thank you for your patience and understanding throughout this process. Should you have any questions or need further assistance, feel free to reach out at any time.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.