cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Exporting and Importing a PowerApp

Is there any way besides the Import/Export function in the PowerApps designer to Export and package a PowerApp and Import it?  Can this be done from PowerShell?

1 ACCEPTED SOLUTION

Accepted Solutions

Hi Everyone,

I did not find any existing idea about this so I created one in the portal.

https://powerusers.microsoft.com/t5/PowerApps-Ideas/PowerShell-Cmdlet-to-publish-deploy-the-form-to-...

Thanks,

Dileep

View solution in original post

6 REPLIES 6
v-xida-msft
Community Support
Community Support

Hi @bboardman,

 

Do you want to Export or Import a PowerApps app with packaging without the Import/Export function in PowerApps?

Do you want to use PowerShell script to Emport/Import a PowerApps app within your PowerApps?

 

If you want to Export or Import a PowerApps app with packaging without the Import/Export function, I afraid that there is no way to achieve your needs in PowerApps currently.

 

Currently, we could only Export/Import a PowerApps app with packaging using Import/Export option within PowerApps designer. Please check the following blog:

https://powerapps.microsoft.com/en-us/blog/powerapps-packaging/

 

If you want to use PowerShell script to Emport/Import a PowerApps app within your PowerApps, I afraid that there is also no way to achieve your needs in PowerApps currently. The supported PowerSheell Cmdlet within PowerApps, please check the following article:

https://docs.microsoft.com/en-us/powerapps/administrator/powerapps-powershell

 

If you would like this feature to be added in PowerApps, please submit an idea to PowerApps Ideas Forum:

https://powerusers.microsoft.com/t5/PowerApps-Ideas/idb-p/PowerAppsIdeas

 

Best regards,

Kris

 

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thank you for your reply.

Hi Everyone,

I did not find any existing idea about this so I created one in the portal.

https://powerusers.microsoft.com/t5/PowerApps-Ideas/PowerShell-Cmdlet-to-publish-deploy-the-form-to-...

Thanks,

Dileep

AlyaKoniPA
Regular Visitor

You are able to import the package like the portal make.powerapps.com is doing it.

 

$UsedBapApiHost = "api.bap.microsoft.com"

Import-Module "Microsoft.PowerApps.Administration.PowerShell"

function Get-AudienceForHostName
{
[CmdletBinding()]
Param(
[string] $Uri
)
$hostMapping = @{
"management.azure.com" = "https://management.azure.com/";
"api.powerapps.com" = "https://service.powerapps.com/";
"tip1.api.powerapps.com" = "https://service.powerapps.com/";
"tip2.api.powerapps.com" = "https://service.powerapps.com/";
"graph.windows.net" = "https://graph.windows.net/";
"api.bap.microsoft.com" = "https://service.powerapps.com/";
"tip1.api.bap.microsoft.com" = "https://service.powerapps.com/";
"tip2.api.bap.microsoft.com" = "https://service.powerapps.com/";
"api.flow.microsoft.com" = "https://service.flow.microsoft.com/";
"tip1.api.flow.microsoft.com" = "https://service.flow.microsoft.com/";
"tip2.api.flow.microsoft.com" = "https://service.flow.microsoft.com/";
}
$uriObject = New-Object System.Uri($Uri)
$audhost = $uriObject.Host
if ($hostMapping[$audhost] -ne $null)
{
return $hostMapping[$audhost];
}
Write-Verbose "Unknown host $audhost. Using https://management.azure.com/ as a default";
return "https://management.azure.com/";
}

function Invoke-Request(
[CmdletBinding()]

[Parameter(Mandatory=$True)]
[string] $Uri,

[Parameter(Mandatory=$True)]
[string] $Method,

[object] $Body = $null,

[Hashtable] $Headers = @{},

[switch] $ParseContent,

[switch] $ThrowOnFailure
)
{
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$audience = Get-AudienceForHostName -Uri $Uri
$token = Get-JwtToken -Audience $audience
$Headers["Authorization"] = "Bearer $token";
$Headers["User-Agent"] = "PowerShell cmdlets 1.0";
try {
if ($Body -eq $null -or $Body -eq "")
{
$response = Invoke-WebRequest -Uri $Uri -Headers $Headers -Method $Method -UseBasicParsing
}
else 
{
$jsonBody = ConvertTo-Json $Body -Depth 20
$response = Invoke-WebRequest -Uri $Uri -Headers $Headers -Method $Method -ContentType "application/json; charset=UTF-8" -Body $jsonBody -UseBasicParsing
}
if ($ParseContent)
{
if ($response.Content)
{
return ConvertFrom-Json $response.Content;
}
}
return $response
} catch {
$response = $_.Exception.Response
if ($_.ErrorDetails)
{
$errorResponse = ConvertFrom-Json $_.ErrorDetails;
$code = $response.StatusCode
$message = $errorResponse.Error.Message
Write-Verbose "Status Code: '$code'. Message: '$message'" 
}
if ($ThrowOnFailure)
{
throw;
}
else 
{
return $response
}
}
}

function Configure-ImportResourcesObject(
$Resources,
$EnvironmentName = $null,
[bool]$DefaultToExportSuggestions = $false,
[bool] $NewApp = $false,
[string] $ResourceName
)
{
$includedResourceIds = @()
$includedSuggestedResourceIds = @()
$includedResources = $Resources
$numResources = 0
$env = Get-AdminPowerAppEnvironment -EnvironmentName $EnvironmentName
$environmentDisplayName = $env.DisplayName
$selectedCommonDataServiceOption = $null
foreach ($resource in Get-Member -InputObject $includedResources -MemberType NoteProperty)
{
$numResources = $numResources + 1 
$property = 'Name'
$propertyvalue = $resource.$property
If($includedResources.$propertyvalue.id -ne $null -and $includedResources.$propertyvalue.id -ne "")
{
$includedResourceIds = $includedResourceIds + $includedResources.$propertyvalue.id
}
If(!$includedSuggestedResourceIds.$propertyvalue.suggestedId)
{
$includedSuggestedResourceIds = $includedSuggestedResourceIds + $includedSuggestedResourceIds.$propertyvalue.suggestedId
}
$type = $null
if ($includedResources.$propertyvalue.type -eq "Microsoft.PowerApps/apps")
{
$result = $null
$selection = $null

if($NewApp)
{
$type = "New"
$includedResources.$propertyvalue.details.displayName = $ResourceName
}
else 
{
$type = "Update"
$selectedResource = $result.selectedResource
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name id -value $selectedResource.id
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name name -value $selectedResource.name
} 
}
if ($includedResources.$propertyvalue.type -eq "Microsoft.Flow/flows")
{
$result = $null
$selection = $null

if($NewApp)
{
$type = "New"
$includedResources.$propertyvalue.details.displayName = $ResourceName
}
else 
{
$type = "Update"
$selectedResource = $result.selectedResource
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name id -value $selectedResource.id
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name name -value $selectedResource.name
}
}
if ($includedResources.$propertyvalue.type -eq "Microsoft.PowerApps/apis")
{
if ($includedResources.$propertyvalue.name -eq $null)
{
if (-Not $NewApp) 
{
$type = "Existing"
$selectedResource = $result.selectedResource
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name id -value $selectedResource.id
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name name -value $selectedResource.name
}
}
else { 
$type = "Existing"
}
}
if ($includedResources.$propertyvalue.type -eq "Microsoft.PowerApps/apis/connections")
{
if (-Not $NewApp) 
{
$type = "Existing"
$selectedResource = $result.selectedResource
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name id -value $selectedResource.id
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name name -value $selectedResource.name
}
}
if ($includedResources.$propertyvalue.type -eq "Microsoft.CommonDataModel/environments/namespaces/enumerations" -or $includedResources.$propertyvalue.type -eq "Microsoft.CommonDataModel/environments/namespaces/entities")
{ 
if ($includedResources.$propertyvalue.configurableBy -eq "User")
{
if($DefaultToExportSuggestions -and ($includedResources.$propertyvalue.suggestedCreationType -ne $null))
{
$type = $includedResources.$propertyvalue.suggestedCreationType
}
else {
If($selectedCommonDataServiceOption -eq $null)
{
$selectedCommonDataServiceOption = "Overwrite"
$type = $selectedCommonDataServiceOption
}
else {
$type = $selectedCommonDataServiceOption
}
}
}
else {
$type = $includedResources.$propertyvalue.suggestedCreationType
}
}
If($type)
{ 
If($includedResources.$propertyvalue.suggestedCreationType)
{
$includedResources.$propertyvalue.suggestedCreationType = $type
}
else
{
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name suggestedCreationType -value $type
}
$includedResources.$propertyvalue | Add-Member -MemberType NoteProperty -name selectedCreationType -value $type
}
}
$responseObject = @{
resources = $includedResources
resourceIds = $includedResourceIds
suggestedResourceIds = $includedSuggestedResourceIds
} 
return $responseObject
}

function Upload-FileToBlogStorage(
[string] $EnvironmentName,
[string] $FilePath,
[string] $ApiVersion = "2016-11-01"
)
{
try {
$fileBinary = [IO.File]::ReadAllBytes($FilePath);
$encoding = [System.Text.Encoding]::GetEncoding("iso-8859-1");
$file = $encoding.GetString($fileBinary)
} catch {
Write-Host "Failed to read the file"
throw
}
$generateResourceStorageUrl = "https://$UsedBapApiHost/providers/Microsoft.BusinessAppPlatform/environments/" + $EnvironmentName + "/generateResourceStorage`?api-version=" + $ApiVersion
$generateResourceStorageResponse = Invoke-Request -Uri $generateResourceStorageUrl -Method POST -ParseContent -ThrowOnFailure
$originalBlobUri = $generateResourceStorageResponse.sharedAccessSignature
$uri = [System.Uri] $originalBlobUri 
$filename = Split-Path $FilePath -Leaf
$uriHost = $uri.Host
$uriPath = $uri.AbsolutePath
$uriQuery = $uri.Query
$tempBlobUri = "https://$uriHost$uriPath/$fileName$uriQuery"
$commitBlobUri = "$tempBlobUri&comp=blocklist"
$uploadBlobUri = "$tempBlobUri&comp=block"
$BlockId = "BlockId"
$Bytes = [System.Text.Encoding]::Unicode.GetBytes($BlockId)
$EncodedBlockId =[Convert]::ToBase64String($Bytes)
$uploadBlobUri = "$uploadBlobUri&blockid=$EncodedBlockId"
try {
$uploadFiletoBLog = Invoke-WebRequest -Uri $uploadBlobUri -Method Put -ContentType "application/json" -Body $file -UseBasicParsing
$commitBody = "<?xml version=`"1.0`" encoding=`"utf-8`"?><BlockList><Latest>$EncodedBlockId</Latest></BlockList>"
$commitFiletoBLog = Invoke-WebRequest -Uri $commitBlobUri -Method Put -ContentType "application/json; charset=UTF-8" -Body $commitBody -UseBasicParsing
} catch {
Write-Host "Failed to upload the file to blob storage"
throw
}
return $tempBlobUri
}

function Get-ImportPackageResources(
[string] $EnvironmentName,
[string] $ImportPackageBlobUri,
[string] $ApiVersion = "2016-11-01"
)
{
$listParametersUri = "https://$UsedBapApiHost/providers/Microsoft.BusinessAppPlatform/environments/" + $EnvironmentName + "/listImportParameters`?api-version=" + $ApiVersion
$listParametersBody = @{ 
packageLink = @{
value = $ImportPackageBlobUri
} 
}
$listParametersResponse = Invoke-Request -Uri $listParametersUri -Method POST -Body $listParametersBody -ThrowOnFailure
$statusUri= $listParametersResponse.Headers['Location']
while($listParametersResponse.StatusCode -ne 200) 
{
Start-Sleep -s 5
$listParametersResponse = Invoke-Request -Uri $statusUri -Method GET -ThrowOnFailure
}
$parsedListParametersResponse = ConvertFrom-Json $listParametersResponse.Content
return $parsedListParametersResponse
}

function Import-Package(
[string] $EnvironmentName,
[string] $ImportPackageFilePath,
[string] $ApiVersion = "2016-11-01",
[bool] $DefaultToExportSuggestions = $false,
[bool] $NewApp = $false,
[string] $ResourceName
)
{
$blobUri = Upload-FileToBlogStorage -EnvironmentName $EnvironmentName -FilePath $ImportPackageFilePath -ApiVersion $ApiVersion
$parsedListParametersResponse = Get-ImportPackageResources -EnvironmentName $EnvironmentName -ImportPackageBlobUri $blobUri -ApiVersion $ApiVersion
$includedResources = Configure-ImportResourcesObject -resources $parsedListParametersResponse.properties.resources -EnvironmentName $EnvironmentName -DefaultToExportSuggestions $DefaultToExportSuggestions -NewApp $NewApp -ResourceName $ResourceName
$validateImportPackageUri = "https://$UsedBapApiHost/providers/Microsoft.BusinessAppPlatform/environments/" + $EnvironmentName + "/validateImportPackage`?api-version=" + $ApiVersion
$validateImportPackageBody = @{ 
details = $parsedListParametersResponse.properties.details
packageLink = $parsedListParametersResponse.properties.packageLink
resources = $includedResources.resources
}
$validateImportPackageResponse = Invoke-Request -Uri $validateImportPackageUri -Method POST -Body $validateImportPackageBody -ThrowOnFailure
$parsedValidateImportResponse = ConvertFrom-Json $validateImportPackageResponse.Content
if(($parsedValidateImportResponse.errors).Length -gt 0)
{
Write-Host "Package failed validation with the following errors \n" + $parsedValidateImportResponse.errors
throw
}
$importPackageUri = "https://$UsedBapApiHost/providers/Microsoft.BusinessAppPlatform/environments/" + $EnvironmentName + "/importPackage`?api-version=" + $ApiVersion
$importPackageResponse = Invoke-Request -Uri $importPackageUri -Method POST -Body $validateImportPackageBody -ThrowOnFailure
$importStatusUri = $importPackageResponse.Headers['Location']
while($importPackageResponse.StatusCode -ne 200) 
{
Start-Sleep -s 5
$importPackageResponse = Invoke-Request -Uri $importStatusUri -Method GET -ThrowOnFailure
}
$parsedImportPackageResponse = ConvertFrom-Json $importPackageResponse.Content
if(($parsedImportPackageResponse.properties.errors).Length -gt 0)
{
Write-Host "Package failed import with the following errors " + $parsedImportPackageResponse.properties.errors
}
return $parsedImportPackageResponse
}


Use the script like:

$PowerAppEnv = Get-AdminPowerAppEnvironment -Default
$PowerAppEnvName = $PowerAppEnv.EnvironmentName
$PowerApp = Get-AdminPowerApp $appTitle
$impAppResp = Import-Package -EnvironmentName $PowerAppEnvName -ImportPackageFilePath "$PathToZipFile" -ResourceName $appTitle -NewApp (-Not $PowerApp)
$impAppResp = Publish-PowerApp $appTitle

 

@AlyaKoniPA Thanks for sharing the snippet. I tried to extend it in order to export packages but get stuck as it seems the same token is not valid for "exportPackage?" part. Any ideas on how to make the export work?

Hi @Mijata 

Use this snippet to export a package:

function Export-Package(
    [string] $EnvironmentName,
    [string] $ExportPackageFilePath,
    [string] $ApiVersion = "2016-11-01",
    [bool]   $DefaultToExportSuggestions = $false,
    [object] $App
)
{

    $getPackageUri = "https://$UsedBapApiHost/providers/Microsoft.BusinessAppPlatform/environments/" + $EnvironmentName + "/listPackageResources`?api-version=" + $ApiVersion
    $getPackageBody = @{ 
        baseResourceIds = @("/providers/Microsoft.PowerApps/apps/$($App.AppName)")
    }
    $getPackageResponse = Invoke-Request -Uri $getPackageUri -Method POST -Body $getPackageBody -ThrowOnFailure
    $getPackageResponse = ConvertFrom-Json $getPackageResponse.Content
    if ($getPackageResponse.Status -ne "Succeeded")
    {
        throw "Error getting package resources"
    }

    $resourceIds = @()
    foreach($resource in $getPackageResponse.resources.PSObject.Properties.Name)
    {
        $resourceIds += $getPackageResponse.resources."$resource".id
    }

    $exportPackageUri = "https://$UsedBapApiHost/providers/Microsoft.BusinessAppPlatform/environments/" + $EnvironmentName + "/exportPackage`?api-version=" + $ApiVersion
    $exportPackageBody = @{
        includedResourceIds = $resourceIds
        details = @{
            displayName = $App.Internal.properties.displayName
            description = $App.Internal.properties.description
            creator = $App.Owner.displayName
            sourceEnvironment = $EnvironmentName
        }
        resources = $getPackageResponse.resources
    }
    $exportPackageResponse = Invoke-Request -Uri $exportPackageUri -Method POST -Body $exportPackageBody -ThrowOnFailure
    $exportPackageJobUri = $exportPackageResponse.Headers['Location']
    $exportPackageResponse = ConvertFrom-Json $exportPackageResponse.Content
    if ($exportPackageResponse.Status -ne "Running" -and $exportPackageResponse.Status -ne "Succeeded")
    {
        throw "Error export package job creation"
    }

    do
    {
        Start-Sleep -Seconds 2
        $exportPackageJob = Invoke-Request -Uri $exportPackageJobUri -Method GET -ThrowOnFailure
        $exportPackageJob = ConvertFrom-Json $exportPackageJob.Content
    } while ($exportPackageJob.properties.status -ne "Succeeded")

    $exportPackageZipUri = $exportPackageJob.properties.packageLink.value
    Invoke-WebRequest -Uri $exportPackageZipUri -Method GET -OutFile $ExportPackageFilePath
}

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (2,457)