Merge pull request #6115 from MicrosoftDocs/2612854-2

Wrap - feature docs - 2612854 - to publish 4/11 or later - ported from #5925

Author: tapanm-MSFT

powerapps-docs/maker/TOC.yml

@@ -1141,6 +1141,18 @@
       href: ./canvas-apps/transform-infopath.md
     - name: Analyze app telemetry using Application Insights
       href: ./canvas-apps/application-insights.md
+  - name: Create native mobile apps (preview)
+    items:
+      - name: Wrap (preview) overview
+        href: ./common/wrap/overview.md
+      - name: Customize and build your mobile app
+        href: ./common/wrap/how-to.md
+      - name: Code sign for iOS
+        href: ./common/wrap/code-sign-ios.md
+      - name: Code sign for Android
+        href: ./common/wrap/code-sign-android.md
+      - name: Frequently asked questions
+        href: ./common/wrap/faq.yml
   - name: For developers
     items:
     - name: Canvas apps for enterprise developers, partners, and ISVs

powerapps-docs/maker/common/wrap/code-sign-android.md

@@ -0,0 +1,111 @@
+---
+title: Code sign for Android (preview)
+description: Learn about how to code sign for Android for Power Apps wrap.
+author: larryk78
+ms.topic: article
+ms.custom: canvas
+ms.reviewer: tapanm
+ms.date: 04/07/2022
+ms.subservice: canvas-maker
+ms.author: lknibb
+search.audienceType: 
+  - maker
+search.app: 
+  - PowerApps
+contributors:
+  - tapanm-msft
+  - larryk78
+---
+
+# Code sign for Android (preview)
+
+[This article is pre-release documentation and is subject to change.]
+
+In this article, you'll learn about how to code sign for Android. You'll need to sign your app for Android if you selected Android as one of the [platforms](overview.md#app-platforms) while creating and building your [wrap project](how-to.md#create-a-wrap-project).
+
+> [!TIP]
+> For general guidance about signing an app for Android platforms, see [Sign your app](https://developer.android.com/studio/publish/app-signing).
+
+## Prepare your PC
+
+You'll need the following information to get started:
+
+- Install [Java™ Platform, Standard Edition Development Kit (JDK™)](https://www.oracle.com/java/technologies/downloads/)
+- Install [Android Studio](https://developer.android.com/studio)
+- Install [OpenSSL](https://www.openssl.org/)
+
+## Generate keys
+
+We'll use [keytool](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html) from Java SDK to create a certificate to sign the application package. Keytool is used to manage a keystore (database) of cryptographic keys, X.509 certificate chains, and trusted certificates.
+
+To generate a key, open a command prompt and run the following command:
+
+`keytool -genkey -alias SIGNATURE_ALIAS -keyalg RSA -keystore PATH_TO_KEYSTORE -keysize 2048 -validity 100`
+
+Parameters:
+
+- **genkey** - command to generate a key.
+- **alias** - indicates the alias to be used in the future to refer to the keystore entry containing the keys that will be generated.
+- **keyalg** - key algorithm name.
+- **keystore** - the name of the keystore you're using.
+- **keysize** - the size of each key to be generated.
+- **validity** - validity of the key in number of days.
+
+More information: [Generate Keys](https://docs.oracle.com/javase/tutorial/security/toolsign/step3.html)
+
+Example:
+
+`keytool -genkey -alias powerappswrap -keyalg RSA -keystore powerappswrap.jks -keysize 2048 -validity 10000`
+
+:::image type="content" source="media/code-sign-android/keytool.png" alt-text="A screenshot with keytool command using the parameters in the above example.":::
+
+## Generate signature hash
+
+After generating the key, we'll use the **exportcert** command in **keytool** to export the keystore certificate.
+
+`keytool -exportcert -alias SIGNATURE_ALIAS -keystore PATH_TO_KEYSTORE | openssl sha1 -binary | openssl base64`
+
+Parameters:
+
+- **exportcert** - reads from the keystore the certificate associated with alias and stores it in the cert_file file. When no file is specified, the certificate is output to stdout.
+- **alias** - the alias used while generating keys [earlier](#generate-keys).
+- **keystore** - the name of the keystore you're using.
+- **openssl** - generates SHA1 key for Android.
+
+## Sign the APK package
+
+The next step is to sign the APK package using **apksigner** tool. The [apksigner tool](https://developer.android.com/studio/command-line/apksigner) allows you to sign APKs and ensure that the APK package signature will be verified successfully on all Android platforms supported by the APKs.
+
+### Find your apksigner
+
+1. Check the Android SDK path in the Android Studio.
+1. Select **Tool** > **SDK Manager** > **Android SDK Location**.
+
+    If using iOS, check the apksigner file from the **buildTools Version** directory:
+
+    Go to **SDK** directory > **build-tools** > **buildToolsVersion** > **lib**, and check the **apksigner.jar** file 
+
+### Use the apksigner file
+
+Run the following command to use the **apksigner** and sign the package:
+
+`apksigner.bat sign --ks PATH_TO_KEYSTORE --ks-key-alias KEY_ALIAS PATH_TO_APK`
+
+Parameters:
+
+- **ks** - path to the keystore.
+- **ks-key-alias** - key alias path to APK file.
+
+When prompted, enter the password.
+
+More information: [Android Studio command line tools: **apksigner**](https://developer.android.com/studio/command-line/apksigner)
+
+## Distribute the app
+
+You can now host the package on a distribution service such as [App Center](how-to.md#test-and-distribute-mobile-app-package). To distribute using Microsoft Intune, see [Add an Android line-of-business app to Microsoft Intune](/mem/intune/apps/lob-apps-android).
+
+### See also
+
+- [Wrap overview (preview)](overview.md)
+- [Manually Signing the APK - Xamarin](/xamarin/android/deploy-test/signing/manually-signing-the-apk)
+- [Code sign on iOS (preview)](code-sign-ios.md)

powerapps-docs/maker/common/wrap/code-sign-ios.md

@@ -0,0 +1,197 @@
+---
+title: Code sign for iOS (preview)
+description: Learn about how to code sign for iOS for Power Apps wrap.
+author: larryk78
+ms.topic: article
+ms.custom: canvas
+ms.reviewer: tapanm
+ms.date: 04/07/2022
+ms.subservice: canvas-maker
+ms.author: lknibb
+search.audienceType: 
+  - maker
+search.app: 
+  - PowerApps
+contributors:
+  - tapanm-msft
+  - larryk78
+---
+
+# Code sign for iOS (preview)
+
+[This article is pre-release documentation and is subject to change.]
+
+In this article, you'll learn about how to code sign for iOS. You'll need to sign your app for iOS if you selected iOS as one of the [platforms](overview.md#app-platforms) while creating and building your [wrap project](how-to.md#create-a-wrap-project).
+
+## Prerequisites
+
+You'll need the following information to get started:
+
+- App ID
+- Device UDIDs (only for testing and development purpose)
+
+You'll also need a macOS device to code sign for iOS.
+
+## Prepare your Mac
+
+Set up your Mac with the following configuration.
+
+1. Install **Xcode**. More information: [Xcode](https://developer.apple.com/support/xcode/)
+1. Install PowerShell for macOS. More information: [Installing PowerShell on macOS](/powershell/scripting/install/installing-powershell-on-macos)
+1. Enroll in [Apple Developer Program](https://developer.apple.com/programs/)
+1. To distribute your apps within the organization, you'll need to sign up for [Apple Enterprise Developer Program](https://developer.apple.com/programs/enterprise/).
+
+## Create App ID
+
+1. Sign in to your developer account by going to <https://developer.apple.com> and selecting the **Account** tab.
+
+    :::image type="content" source="media/code-sign-ios/account-tab.png" alt-text="Account tab.":::
+
+1. Go to [**Certificates, IDs & Profiles &gt; Identifiers**](https://developer.apple.com/account/resources/identifiers/list).
+
+1. Select **+** to create a new identifier.
+
+    :::image type="content" source="media/code-sign-ios/identifier.png" alt-text="Create new identifier.":::
+
+1. Select **App IDs**, and then select **Continue**.
+
+    :::image type="content" source="media/code-sign-ios/register-identifier.png" alt-text="Register a new identifier.":::
+
+1. Select the type as **App**, and then select **Continue**.
+
+1. Register an **App ID**:
+
+    :::image type="content" source="media/code-sign-ios/register-appid.png" alt-text="Register an App ID.":::
+
+    1. **Description** - Name of your app.
+    1. **Bundle ID** - select **Explicit Bundle ID**.
+    1. Enter the bundle ID that you used while [creating the wrap project](how-to.md#bundle-id). More information: [Bundle ID](overview.md#bundle-id)
+    1. Enable the following capabilities:
+        - Associated Domains
+        - iCloud
+        - NFC Tag Reading
+        - Push Notifications
+    1. Select **Continue**.
+
+1. Review, and register the App ID.
+
+## Create a distribution certificate
+
+To create a distribution certificate, create a new certificate signing request first.
+
+### Create Certificate Signing Request (CSR)
+
+1. On your Mac PC, go to the **Applications** folder > **Utilities** > open **Keychain Access**.
+
+1. Select **Keychain Access** > **Certificate Assistant** > **Request a Certificate from a Certificate Authority**.
+
+    :::image type="content" source="media/code-sign-ios/cert-req.png" alt-text="Request a certificate from a CA.":::
+
+1. Fill out the **Certificate Information** as explained below, and then select **Continue**.
+    1. In the **User Email Address** field, enter your Apple ID email address to identify with this certificate.
+    1. In the **Common Name** field, enter your name.
+    1. In the **Request** group, select **Saved to disk**.
+    1. Save the file to your Mac PC.
+
+## Create the distribution certificate
+
+1. Sign in to your developer account at <https://developer.apple.com> by selecting the **Account** tab.
+
+1. Go to [Certificates, IDs & Profiles &gt; Certificates](https://developer.apple.com/account/resources/certificates/list).
+
+    1. Select **+** to create a new certificate.
+    1. Select **App Store and Ad Hoc** > **Continue**.
+
+        ![Certificates, Identifiers & Profiles](media/code-sign-ios/new-cert.png)
+
+        > [!NOTE]
+        > If you have an Enterprise Developer Account then you'll have the option to create an Enterprise Distribution certificate.
+
+1. Upload the Certificate Signing Request (CSR) file that was generated in the previous steps.
+
+    :::image type="content" source="media/code-sign-ios/upload-cert.png" alt-text="Upload the certificate.":::
+
+1. Select **Continue**, and download the certificate to your Mac PC.
+
+1. Double-click the downloaded .cer file to install to Keychain Access.
+
+1. Take a note of the **Name** of the certificate (usually like **iPhone Distribution: Name (Team ID)**). This value is the code signing identity that needs to be provided for signing.
+
+## Add all the devices where the iPA needs to be installed
+
+1. Sign in to your developer account at <https://developer.apple.com> by selecting the **Account** tab.
+
+1. Go to [Certificates, IDs & Profiles &gt; Devices](https://developer.apple.com/account/resources/devices/list).
+
+1. Select **+** to register one or more devices.
+
+1. Enter the **Device Name** and **Device ID (UDID)**.
+
+    :::image type="content" source="media/code-sign-ios/register-device.png" alt-text="Register a device.":::
+
+1. Select **Save**.
+
+    > [!TIP]
+    > You can also register multiple devices together by uploading a list of UDID's.
+
+## Create an iOS Provisioning Profile
+
+1. Sign in to your developer account by going to <https://developer.apple.com> and selecting the **Account** tab.
+
+1. Go to [**Certificates, IDs & Profiles &gt; Profiles**](https://developer.apple.com/account/resources/profiles/list).
+
+1. Select **+** to create a new profile.
+
+1. Select **Ad Hoc** > **Continue**.
+
+    :::image type="content" source="media/code-sign-ios/ad-hoc.png" alt-text="Ad Hoc.":::
+
+    > [!NOTE]
+    > For production testing and development purpose, use **App Store** distribution method.
+
+1. Select App ID that you created earlier, and then select **Continue**.
+
+    :::image type="content" source="media/code-sign-ios/app-id.png" alt-text="App ID.":::
+
+1. Select the certificate that you created earlier, and then select **Continue**.
+
+    :::image type="content" source="media/code-sign-ios/select-cert.png" alt-text="Select certificate.":::
+
+1. Select all the test devices where you want to install your app, and then select **Continue**.
+
+    :::image type="content" source="media/code-sign-ios/add-devices.png" alt-text="Add devices.":::
+
+1. Review and name the provisioning profile. Note down the name of the provisioning profile.
+
+1. Generate and download the profile to your Mac.
+
+1. Double-click to open the downloaded file (\*.mobileprovision) to register it with Xcode.
+
+## Sign the iOS Archive
+
+1. Download the .zip app package created as a result of the [wrap project](how-to.md#create-a-wrap-project).
+
+1. Unzip the package.
+
+    For example, a sample build project **iOS-Archive.zip** file downloaded from the App Center shows a folder structure like below.
+
+    :::image type="content" source="media/code-sign-ios/folder-structure.png" alt-text="Folder structure.":::
+
+1. Open terminal, and change directory to the folder. In this example, **com_single_wrap**.
+
+1. Enter `pwsh` to start PowerShell in the terminal.
+
+1. Run `./SignAndGenerateIPA.ps1` with the values for the "CodeSigningIdentity" and "ProvisioningProfilePath" parameters.
+
+    :::image type="content" source="media/code-sign-ios/powershell.png" alt-text="Run PowerShell script.":::
+
+1. After the script finishes, you'll see an .ipa  file created. In this example, **com_single_wrap.ipa**.
+
+    :::image type="content" source="media/code-sign-ios/package.png" alt-text="IPA package.":::
+
+1. Install the .ipa file in the registered devices using the **Finder** app. You can also host it on a distribution service such as [App Center](how-to.md#test-and-distribute-mobile-app-package). To distribute using Microsoft Intune, see [Add an iOS/iPadOS line-of-business app to Microsoft Intune](/mem/intune/apps/lob-apps-ios).
+
+### See also
+
+- [Wrap overview (preview)](overview.md)
+- [Code sign on Android (preview)](code-sign-android.md)

powerapps-docs/maker/common/wrap/faq.yml

@@ -0,0 +1,49 @@
+### YamlMime:FAQ
+metadata:
+  title: Frequently asked questions for Wrap (preview)
+  description: Frequently asked questions for Wrap (preview).
+  author: larryk78
+  ms.topic: faq
+  ms.custom: 
+  ms.date: 04/07/2022
+  ms.author: lknibb
+  ms.reviewer: tapanm
+  contributors:
+    - larryk78
+    - tapanm-msft
+title: Frequently asked questions for Wrap (preview)
+summary: |
+  Frequently asked questions about the **wrap** feature are listed below. If you don't find an answer to your question, send an email to <[email protected]> with your question.
+
+sections:
+  - name: General
+    questions:
+      - question: |
+          Can I create mobile apps with Power Apps?
+        answer: |
+          Yes. More information: [Creating mobile apps with Power Apps](overview.md)
+
+      - question: |
+          If I create a mobile app with Power Apps, does Microsoft release it for me?
+        answer: |
+          No. Microsoft will wrap your Power Apps app in a native mobile app shell for you to digitally sign and distribute.
+
+      - question: |
+          How do I digitally sign my mobile app?
+        answer: |
+          Signing instructions are provided for [Android](code-sign-android.md) and [iOS](code-sign-ios.md).
+
+      - question: |
+          How do I distribute my mobile app?
+        answer: |
+          It depends on your business scenario. You can use [Microsoft Intune](/mem/intune/fundamentals/what-is-intune), [Managed Google Play](https://support.google.com/googleplay/work/answer/6138458) or [Apple Business Manager](https://developer.apple.com/custom-apps/). 
+
+      - question: |
+          What are Primary and Secondary apps in the context of wrap?
+        answer: |
+          Primary app provides the main experience of your mobile app. Secondary apps are bundled for performance reasons and must be linked from your primary app. See [wrap multiple canvas apps together](overview.md#wrap-multiple-canvas-apps-together).
+
+      - question: |
+          Can I create B2C mobile apps with Power Apps?
+        answer: |
+          No. Power Apps is a platform for creating business applications and uses Azure Active Directory authentication. The wrap feature wraps existing canvas apps for the same set of end users.