You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/build-and-package.md
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Build and package plug-in code
3
3
description: Learn about building plug-in code into assemblies and packages for later registration and upload to the Microsoft Dataverse service.
4
-
ms.date: 11/02/2023
4
+
ms.date: 02/20/2024
5
5
ms.reviewer: pehecke
6
6
ms.topic: article
7
7
author: divkamath
@@ -73,7 +73,6 @@ When you register individual plug-in assemblies without the dependent assemblies
73
73
The following limitations apply when using plug-in dependent assemblies.
74
74
75
75
-[Workflow extensions](workflow/workflow-extensions.md), also known as *custom workflow activities* aren't supported when using the dependent assemblies capability.
76
-
- Plug-ins for virtual table data providers aren't supported.
77
76
- On-premises environments aren't supported.
78
77
- Un-managed code isn't supported. You can't include references to unmanaged resources.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/add-app-solution-default.md
+12-8Lines changed: 12 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ The following table summarizes the methods that allow you to create cloud flows
68
68
|[Create a cloud flow from the Excel add-in](/business-applications-release-notes/april18/microsoft-flow/build-run-flows-excel)| Yes |
69
69
|[Create a cloud flow from the Power Automate mobile app](/power-automate/mobile/mobile-create-flow)| Yes |
70
70
|[Create a cloud flow from SharePoint](https://support.microsoft.com/office/create-a-flow-for-a-list-or-library-a9c3e03b-0654-46af-a254-20252e580d01)| Yes |
71
-
| Create a cloud flow from Project Roadmap |No, ETA November|
71
+
| Create a cloud flow from Project Roadmap |Yes|
72
72
73
73
> [!IMPORTANT]
74
74
> Unsupported entry points will fail to create any cloud flow until that support is added to create a solution cloud flow with that entry point. You must first create a cloud flow in a solution using a supported method.
@@ -95,7 +95,7 @@ Once the feature is enabled, use solutions [export](../data-platform/export-solu
95
95
96
96
Take the following considerations into account before you decide to create canvas apps and cloud flows in a solution by default.
97
97
98
-
- Your Dataverse environment capacity consumption and related cost may increase.
98
+
- Your Dataverse environment capacity consumption and related cost might increase.
99
99
100
100
- Known solution limitations related to canvas apps still apply to canvas apps created in solutions by default.
101
101
@@ -109,15 +109,19 @@ Take the following considerations into account before you decide to create canva
109
109
110
110
- Non-solution canvas apps and non-solution cloud flows can be added into a solution to add them into Dataverse, but there's no way to revert back.
111
111
112
-
## Known issues
113
-
114
-
- The **Monitor** > **Cloud flow activity** page doesn't support solution cloud flows.
112
+
## Improvements
115
113
116
-
-[Audit log events for cloud flow permissions](/power-platform/admin/logging-power-automate#see-audited-events) that provide visibility into sharing aren't updated for solution cloud flows.
114
+
The following scenarios were improved to support cloud flows and canvas apps defined in Dataverse:
117
115
118
-
- The [List Flows as Admin API](/connectors/flowmanagement/#list-flows-as-admin) doesn't return solution cloud flows that haven't previously been turned on (published). The identifier returned is the Logic Apps ID, and unpublished flows don't have one. This API will be updated later to return all solution cloud flows.
116
+
- The **Monitor** > **Cloud flow activity** page now supports solution cloud flows.
117
+
- The [List My Flows API](/connectors/flowmanagement/#list-my-flows) doesn't return any solution cloud flows.
118
+
119
+
## Known issues
119
120
120
-
- The [List Flows API](/connectors/flowmanagement/#list-my-flows) doesn't return any solution cloud flows. This will be updated later to return solution cloud flows when the [List Flows as Admin API](/connectors/flowmanagement/#list-flows-as-admin) is updated.
121
+
-[Audit log events for cloud flow permissions](/power-platform/admin/logging-power-automate#see-audited-events) that provide visibility into sharing aren't updated for solution cloud flows.
122
+
- The [List Flows as Admin API](/connectors/flowmanagement/#list-flows-as-admin) doesn't return solution cloud flows that haven't previously been turned on (published). This API is updated to return all solution cloud flows.
123
+
- Flows with delegated authentication to Roadmap can't be added into a solution and migrated to Dataverse.
124
+
- You can't add flows with delegated authentication to SharePoint into a solution and migrate them into Dataverse directly. However, you can remove the delegated authentication to allow migration and then add it back after migration.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/common/wrap/code-sign-ios.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -175,7 +175,7 @@ To create a distribution certificate, create a new certificate signing request f
175
175
1. If signing with enterprise certificate, open the **Distribution-exportOptions.plist** file. Open the folder with Xcode and change the value for the **method** field inside the file to **enterprise**.
176
176
177
177
> [!NOTE]
178
-
> Enterprise signing is not supported with Keyvault signing.
178
+
> Enterprise signing is not supported with Key Vault signing.
179
179
180
180
1. Open terminal, and change directory to the unzipped folder.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/common/wrap/create-key-vault-for-code-signing.md
+18-17Lines changed: 18 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Create key vault for code signing
3
-
description: Learn how to create Azure key vault for automated code signing of native mobile apps in wrap wizard.
2
+
title: Create Key Vault for code signing
3
+
description: Learn how to create Azure Key Vault for automated code signing of native mobile apps in wrap wizard.
4
4
author: makolomi
5
5
ms.topic: article
6
6
ms.custom: canvas
@@ -13,12 +13,12 @@ search.audienceType:
13
13
contributors:
14
14
- mkaur-msft
15
15
---
16
-
# Create Azure key vault for wrap in Power Apps
16
+
# Create Azure Key Vault for wrap in Power Apps
17
17
18
-
In order to automatically, sign your Android or iOS mobile app package during [Step 2](wrap-how-to.md#step-2-target-platform) of the wrap wizard, it's necessary to have Azure Key Vault configured. Azure Key Vault is a cloud-based service designed to provide a secure storage solution for secrets, which can include certificates, passwords, keys, and other sensitive information. To learn more about Azure Key Vault, see [Introduction to Azure key vault](/azure/key-vault/general/overview).
18
+
In order to automatically, sign your Android or iOS mobile app package during [Step 2](wrap-how-to.md#step-2-target-platform) of the wrap wizard, it's necessary to have Azure Key Vault configured. Azure Key Vault is a cloud-based service designed to provide a secure storage solution for secrets, which can include certificates, passwords, keys, and other sensitive information. To learn more about Azure Key Vault, see [Introduction to Azure Key Vault](/azure/key-vault/general/overview).
19
19
20
20
21
-
In this article, you will learn how to use an existing Azure key vault or create a new [Azure portal](https://portal.azure.com).
21
+
In this article, you will learn how to use an existing Azure Key Vault or create a new [Azure portal](https://portal.azure.com).
22
22
23
23
## Prerequisites
24
24
@@ -28,15 +28,15 @@ In this article, you will learn how to use an existing Azure key vault or create
28
28
- Create a [distribution certificate](code-sign-ios.md#create-the-distribution-certificate) or [ad-hoc Provisioning Profile](code-sign-ios.md#create-an-ios-provisioning-profile) or enterprise provisioning profile.
29
29
30
30
31
-
## Create Azure key vault and configure KeyVault URI
31
+
## Create Azure Key Vault and configure Key Vault URI
32
32
33
33
1. To create a new Azure service principal for the 1P Microsoft Entra application **4e1f8dc5-5a42-45ce-a096-700fa485ba20 (WrapKeyVaultAccessApp)**, sign in to your tenant as an admin. Then, run the following script in PowerShell:
2. Follow these steps to ensure that the Service Principal representing your app, such as Wrap KeyVault Access App, has the necessary access permissions, add a **Reader** role assignment to it in the **Access Control (IAM)** of your default subscription. This should also be present in the IAM of both the subscription and the Keyvault.
39
+
2. Follow these steps to ensure that the Service Principal representing your app, such as Wrap Key Vault Access App, has the necessary access permissions, add a **Reader** role assignment to it in the **Access Control (IAM)** of your default subscription. This should also be present in the IAM of both the subscription and the Key Vault.
40
40
41
41
1. On the left select **Access control (IAM)** tab and then select **Add** > **Add role assignment**.
42
42
@@ -45,26 +45,26 @@ In this article, you will learn how to use an existing Azure key vault or create
45
45
> [!div class="mx-imgBorder"]
46
46
> ![Select the Members tab.](media/how-to-v2/Add_members.png"Select the Members tab.")
47
47
48
-
4. On **Members** tab, select **Select member** and in the text box on the right enter **Wrap KeyVault Access App** and search for it.
48
+
4. On **Members** tab, select **Select member** and in the text box on the right enter **Wrap Key Vault Access App** and search for it.
49
49
50
50
> [!div class="mx-imgBorder"]
51
-
> ![Search for Wrap KeyVault Access App.](media/how-to-v2/Add_role_assignment.png"Search for Wrap KeyVault Access App.")
51
+
> ![Search for Wrap Key Vault Access App.](media/how-to-v2/Add_role_assignment.png"Search for Wrap Key Vault Access App.")
52
52
53
-
5. Select **Wrap KeyVault Access App** and then select **Review + assign** to assign the **Reader** role.
53
+
5. Select **Wrap Key Vault Access App** and then select **Review + assign** to assign the **Reader** role.
54
54
55
55
> [!div class="mx-imgBorder"]
56
56
> ![Assign Reader role to Wrap KeyVault Access App.](media/how-to-v2/Add_role_for_wrap_signing.png"Assign Reader role to Wrap KeyVault Access App.")
57
57
58
58
59
-
3. Create or access existing key vault. Make sure this key vault is located in the default subscription for your tenant. More information: [Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal).
59
+
3. Create or access existing Key Vault. Make sure this Key Vault is located in the default subscription for your tenant. More information: [Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal).
60
60
61
-
4. Add access policies for the key vault.
61
+
4. Add access policies for the Key Vault.
62
62
63
63
5. Choose one of the following options based on your device:
64
64
65
65
-**Android**
66
66
67
-
Generate the .pfx file and then proceed to upload it to the certificate section of the keyvault. More information: [Generate keys](code-sign-android.md#generate-keys)
67
+
Generate the .pfx file and then proceed to upload it to the certificate section of the Key Vault. More information: [Generate keys](code-sign-android.md#generate-keys)
68
68
69
69
:::image type="content" source="media/wrap-canvas-app/wrap-1.png" alt-text="Create a cert for Android.":::
70
70
@@ -73,16 +73,17 @@ In this article, you will learn how to use an existing Azure key vault or create
73
73
74
74
-**iOS**
75
75
1. Select the .cer into Keychain Access app to install it. For more information, see [Create the distribution certificate](code-sign-ios.md#create-the-distribution-certificate).
76
-
2. Right-click your certificate file to export the file as a .p12 file, select **Export**, and then select the file format .p12.
76
+
2. Right-click your certificate file to export the file as a .p12 file, select **Export**, and then select the file format .p12.
77
+
3. The iOS Certificate extension (.p12) should be renamed to **.pfx** as it is the accepted format by Key Vault
77
78
78
79
> [!NOTE]
79
-
> When you upload to the keyvault, you'll need to provide the password that you set in previous step for the .p12 file.
80
+
> When you upload to the Key Vault, you'll need to provide the password that you set in previous step for the .p12 file.
80
81
81
82
3.[Create the provisioning profile](code-sign-ios.md#create-an-ios-provisioning-profile) and run this command to encode it to base64:
82
83
- Mac: base64 `-i example.mobileprovision`
83
84
- Windows: `certutil -encode data.txt tmp.b64`
84
85
85
-
4. Upload the `base64` string obtained from the previous step to the Keyvault secret. Next, upload the .p12 file to Keyvault Certificate.
86
+
4. Upload the `base64` string obtained from the previous step to the Key Vault secret. Next, upload the .pfx file to Key Vault Certificate.
86
87
87
88
88
89
:::image type="content" source="media/wrap-canvas-app/wrap-2.png" alt-text="Create a cert for iOS.":::
@@ -102,4 +103,4 @@ For Troubleshooting issues, see [Troubleshoot issues with the wrap feature in Po
102
103
-[Code sign for iOS](code-sign-ios.md)
103
104
-[Code sign for Android](code-sign-android.md)
104
105
-[Code sign for Google Play Store](https://developer.android.com/studio/publish/app-signing)
Copy file name to clipboardExpand all lines: powerapps-docs/maker/common/wrap/faq.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ sections:
41
41
- question: |
42
42
How do I digitally sign my mobile app?
43
43
answer: |
44
-
You can automatically sign your mobile app package in **Step 2: Target Platforms** step in wrap wizard. You will need to [create and prepare your Azure key vault](create-key-vault-for-code-signing.md) to take advantage of automatic mobile app signing feature in wrap wizard. For information on how to code sign your app manually, see instructions here: [Android](code-sign-android.md), [iOS](code-sign-ios.md) and [Google Play Store](https://developer.android.com/studio/publish/app-signing).
44
+
You can automatically sign your mobile app package in **Step 2: Target Platforms** step in wrap wizard. You will need to [create and prepare your Azure Key Vault](create-key-vault-for-code-signing.md) to take advantage of automatic mobile app signing feature in wrap wizard. For information on how to code sign your app manually, see instructions here: [Android](code-sign-android.md), [iOS](code-sign-ios.md) and [Google Play Store](https://developer.android.com/studio/publish/app-signing).
45
45
46
46
- question: |
47
47
Can I use Xcode to digitally sign my mobile apps for iOS?
Copy file name to clipboardExpand all lines: powerapps-docs/maker/common/wrap/wrap-how-to.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.custom: canvas
7
7
ms.reviewer: mkaur
8
8
ms.date: 2/9/2023
9
9
ms.subservice: canvas-maker
10
-
ms.author: makolomi
10
+
ms.author: clromano
11
11
search.audienceType:
12
12
- maker
13
13
contributors:
@@ -90,7 +90,7 @@ More information: [Add an app to a solution](../../canvas-apps/add-app-solution.
90
90
2. Under **Target platforms(s)**, select all the mobile platforms that your end users use on their mobile devices.
91
91
92
92
3. Set the **Sign my app** toggle to **ON** to automatically code sign your mobile app, then select the **Azure Key Vault URI** from the list and click **Next**.
93
-
If you don't have any entries in **Azure Key Vault URI** list, you need to create **Azure Key Vault** first. More information: [Create Azure key valut for wrap for Power Apps](create-key-vault-for-code-signing.md).
93
+
If you don't have any entries in **Azure Key Vault URI** list, you need to create **Azure Key Vault** first. More information: [Create Azure Key Vault for wrap for Power Apps](create-key-vault-for-code-signing.md).
94
94
95
95
> [!div class="mx-imgBorder"]
96
96
> 
@@ -258,5 +258,5 @@ You can automatically sign your mobile app package during wrap process in **Step
258
258
- [Code sign for iOS](code-sign-ios.md)
259
259
- [Code sign for Android](code-sign-android.md)
260
260
- [Code sign for Google Play Store](https://developer.android.com/studio/publish/app-signing)
261
-
- [Create your Azure key vault for automated code signing](create-key-vault-for-code-signing.md)
262
-
- [Frequently asked questions for wrap](faq.yml)
261
+
- [Create your Azure Key Vault for automated code signing](create-Key-Vault-for-code-signing.md)
Copy file name to clipboardExpand all lines: powerapps-docs/maker/model-driven-apps/channel-overview.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Release channel for your model-driven app | MicrosoftDocs"
3
3
description: "This article outlines how release channels enable features within a model-driven app."
4
4
ms.custom: ""
5
-
ms.date: 11/06/2023
5
+
ms.date: 2/19/2024
6
6
ms.reviewer: "matp"
7
7
ms.service: powerapps
8
8
ms.subservice: mda-maker
@@ -51,15 +51,15 @@ Model-driven apps release updates every week, which is gradually rolled out to g
51
51
1. Europe
52
52
1. United States
53
53
54
-
The monthly release is the first weekly release of each month. The release matches ```YYMM.1``` where ```YY``` is the release year and ```MM``` is the release month. The monthly release notes are published to [Released versions for Power Apps](/power-platform/released-versions/powerapps) four weeks before the release reaches the region group 2. Region group 2 is used because it's the first region group for production customer environments and region group 1 is used for customer early validation.
54
+
The monthly release is the first weekly release of each month. The release typically matches ```YYMM.1``` where ```YY``` is the release year and ```MM``` is the release month. The monthly release notes are published to [Released versions for Power Apps](/power-platform/released-versions/powerapps) four weeks before the release reaches the region group 2. Region group 2 is used because it's the first region group for production customer environments and region group 1 is used for customer early validation.
55
55
56
56
| Monthly release | Doc published | Feature release | Group 1 | Group 2 | Group 3 | Group 4 | Group 5 |
0 commit comments