erikre-oob2208-15363982 1.3

Author: Erikre

memdocs/intune/developer/app-sdk-android-appendix.md

@@ -32,7 +32,7 @@ ms.custom: intune-classic
 
 # Microsoft Intune App SDK for Android developer guide
 
-The Microsoft Intune App SDK for Android lets you incorporate Intune app protection policies (also known as **APP*- or MAM policies) into your native Java/Kotlin Android app. An Intune-managed application is one that is integrated with the Intune App SDK. Intune administrators can easily deploy app protection policies to your Intune-managed app when Intune actively manages the app.
+The Microsoft Intune App SDK for Android lets you incorporate Intune app protection policies (also known as **APP** or MAM policies) into your native Java/Kotlin Android app. An Intune-managed application is one that is integrated with the Intune App SDK. Intune administrators can easily deploy app protection policies to your Intune-managed app when Intune actively manages the app.
 
 ## Stage Goals
 The guide contains greater detail about the Intune App SDK's architecture, information about uncommon integration steps, and other helpful content.

memdocs/intune/developer/app-sdk-android-phase1.md

@@ -32,9 +32,9 @@ ms.custom: intune-classic
 
 # Intune App SDK for Android - Plan the integration
 
-The Microsoft Intune App SDK for Android lets you incorporate Intune app protection policies (also known as **APP*- or MAM policies) into your native Java/Kotlin Android app. An Intune-managed application is one that is integrated with the Intune App SDK. Intune administrators can easily deploy app protection policies to your Intune-managed app when Intune actively manages the app.
+The Microsoft Intune App SDK for Android lets you incorporate Intune app protection policies (also known as **APP** or MAM policies) into your native Java/Kotlin Android app. An Intune-managed application is one that is integrated with the Intune App SDK. Intune administrators can easily deploy app protection policies to your Intune-managed app when Intune actively manages the app.
 
-# Stage 1: Plan the Integration
+## Stage 1: Plan the Integration
 
 This guide is for Android developers who are looking to add support for Microsoft Intune's App Protection Policies inside their existing Android app.
 
@@ -80,7 +80,7 @@ Your app can skip integrating MSAL **only if all of the following are true**:
 - Your application doesn't need to support non-Intune accounts.
 - Your application doesn't grant access to any resources protected by Conditional Access.
 
-If your app satisfies **all of the above conditions*- and doesn't integrate MSAL, it can still be protected by App Protection Policy, albeit with no option for unmanaged usage. See [Default Enrollment] for details.
+If your app satisfies **all of the above conditions** and doesn't integrate MSAL, it can still be protected by App Protection Policy, albeit with no option for unmanaged usage. See [Default Enrollment] for details.
 
 See [Stage 2: The MSAL Prerequisite] for instructions on integrating MSAL and additional details on identity scenarios inside your application.
 
@@ -96,7 +96,7 @@ If so, your application is **single-identity**.
 Does your application display multiple accounts' data on a shared screen?
 Does your application store multiple accounts' data?
 Does your application let users switch between different logged in accounts?
-If so, your application is **multi-identity*- and you'll need to follow [Stage 5: Multi-Identity]. **This section is required for your app.**
+If so, your application is **multi-identity** and you'll need to follow [Stage 5: Multi-Identity]. **This section is required for your app.**
 
 Even if your application is multi-identity, follow this integration guide in order.
 Initially integrating and testing as single-identity will help ensure proper integration and prevent bugs where corporate data ends up unprotected.
@@ -133,7 +133,7 @@ See [Policy for protecting backup data] in [Stage 7: App Participation Features]
 feature that can be used to control access to AAD resources.
 Intune administrators can define CA rules that allow resource access only from devices or apps that are managed by Intune.
 
-Intune supports two types of CA: **device-based CA*- and **app-based CA**, also known as [App Protection CA].
+Intune supports two types of CA: **device-based CA** and **app-based CA**, also known as [App Protection CA].
 Device-based CA blocks access to protected resources until the entire device is managed by Intune.
 App-based CA blocks access to protected resources until the specific app is managed by Intune App Protection Policies.
 
@@ -155,7 +155,7 @@ The Intune App SDK for Android relies on the presence of the [Company Portal] ap
 > When the Company Portal app is not on the device, an SDK-integrated app behaves the same as a normal app that does not support Intune app protection policies.
 > Even if the Company Portal app is on the device, an SDK-integrated app behaves the same as a normal when the end user is not targeted with app protection policy.
 
-The user is ***not**- required to sign into or even launch the Company Portal app for App Protection Policy to function.
+The user is ***not*** required to sign into or even launch the Company Portal app for App Protection Policy to function.
 
 ### Android versions
 
@@ -195,7 +195,7 @@ To create a new account:
 Before you test app protection policy settings within your own application, it's helpful to familiarize yourself with how these settings behave inside other SDK-integrated applications.
 
 > [!TIP]
-> If your app isn't listed in the Microsoft Endpoint Manager portal, you can target it with a policy by selecting the **more apps*- option and providing the package name in the text box.  
+> If your app isn't listed in the Microsoft Endpoint Manager portal, you can target it with a policy by selecting the **more apps** option and providing the package name in the text box.  
 > You must target your app with app protection policy and deploy the policy to a user to successfully test your integration.  
 > Even if policy is targeted and deployed, your app will not properly enforce policies until it has successfully integrated the SDK.
 

memdocs/intune/developer/app-sdk-android-phase2.md

@@ -32,12 +32,12 @@ ms.custom: intune-classic
 
 # Intune App SDK for Android - Understand the MSAL Prerequisite
 
-The Microsoft Intune App SDK for Android lets you incorporate Intune app protection policies (also known as **APP*- or MAM policies) into your native Java/Kotlin Android app. An Intune-managed application is one that is integrated with the Intune App SDK. Intune administrators can easily deploy app protection policies to your Intune-managed app when Intune actively manages the app.
+The Microsoft Intune App SDK for Android lets you incorporate Intune app protection policies (also known as **APP** or MAM policies) into your native Java/Kotlin Android app. An Intune-managed application is one that is integrated with the Intune App SDK. Intune administrators can easily deploy app protection policies to your Intune-managed app when Intune actively manages the app.
 
 > [!NOTE]
 > This guide is divided into several distinct stages. Start by reviewing [Plan the Integration](..\developer\app-sdk-android-phase1.md).
 
-# Stage 2: The MSAL Prerequisite
+## Stage 2: The MSAL Prerequisite
 
 ## Stage Goals
 
@@ -66,7 +66,7 @@ To learn more about MSAL, see the [MSAL Wiki] and [list of MSAL libraries].
 ## Register your Application with AAD
 
 Before integrating MSAL into your Android application, follow the instructions to [register your application with Azure Active Directory].
-This will generate a **Client ID*- for your application.
+This will generate a **Client ID** for your application.
 
 Next, follow the instructions to [give your app access to the Intune app protection service].
 
@@ -117,12 +117,12 @@ These settings include:
 | Setting | Description | Required for MSAL? | Required by Intune? |
 | - | - | - | - |
 | `ClientID`             | The AAD ClientID (also known as the "Application ID") for your app. <br> There's no default `ClientID`. Use the `ClientID` from [Register your Application with AAD] for your app. |  Yes | No |
-| `Authority`            | The AAD authority to issue a token. <br> By default, this value is the AAD public environment. If overridden, the AAD authority entered will issue the token for your application, which allows authentication to non-default environments, such as Sovereign clouds. | No | If your application requires a non-default authority, yes. **Most apps should not set the Authority parameter.*- |
-| `SkipBroker`           | Boolean value for altering the default MSAL SSO behavior. <br> By default, this value is "false". | No | If your app doesn't support brokered authentication/device-wide SSO, yes and set `SkipBroker` to "true". **Most apps should not set the SkipBroker parameter.*- |
-| `NonBrokerRedirectURI` | [AAD redirect URI] to use in broker-less cases. By default, this value isn't present. | No | If the `SkipBroker` setting is set to "true" and your app requires a redirect URI, yes. **Most apps should not set the NonBrokerRedirectURI parameter.*- |
+| `Authority`            | The AAD authority to issue a token. <br> By default, this value is the AAD public environment. If overridden, the AAD authority entered will issue the token for your application, which allows authentication to non-default environments, such as Sovereign clouds. | No | If your application requires a non-default authority, yes. **Most apps should not set the Authority parameter.** |
+| `SkipBroker`           | Boolean value for altering the default MSAL SSO behavior. <br> By default, this value is "false". | No | If your app doesn't support brokered authentication/device-wide SSO, yes and set `SkipBroker` to "true". **Most apps should not set the SkipBroker parameter.** |
+| `NonBrokerRedirectURI` | [AAD redirect URI] to use in broker-less cases. By default, this value isn't present. | No | If the `SkipBroker` setting is set to "true" and your app requires a redirect URI, yes. **Most apps should not set the NonBrokerRedirectURI parameter.** |
 
 > [!CAUTION]
-> Applications that do not integrate MSAL **must not*- include any of these 4 properties in the manifest.
+> Applications that do not integrate MSAL **must not** include any of these 4 properties in the manifest.
 
 For more detail on non-Intune-specific MSAL configuration options, see [Android Microsoft Authentication Library configuration file].
 

memdocs/intune/developer/app-sdk-android-phase3.md

@@ -32,12 +32,12 @@ ms.custom: intune-classic
 
 # Intune App SDK for Android - Get started with MAM
 
-The Microsoft Intune App SDK for Android lets you incorporate Intune app protection policies (also known as **APP*- or MAM policies) into your native Java/Kotlin Android app. An Intune-managed application is one that is integrated with the Intune App SDK. Intune administrators can easily deploy app protection policies to your Intune-managed app when Intune actively manages the app.
+The Microsoft Intune App SDK for Android lets you incorporate Intune app protection policies (also known as **APP** or MAM policies) into your native Java/Kotlin Android app. An Intune-managed application is one that is integrated with the Intune App SDK. Intune administrators can easily deploy app protection policies to your Intune-managed app when Intune actively manages the app.
 
 > [!NOTE]
 > This guide is divided into several distinct stages. Start by reviewing [Plan the Integration](..\developer\app-sdk-android-phase1.md).
 
-# Stage 3: Getting Started with MAM
+## Stage 3: Getting Started with MAM
 
 ## Stage Goals
 
@@ -78,14 +78,14 @@ The Intune App SDK consists of the following files:
 ## Referencing Intune App libraries
 
 The Intune App SDK is a standard Android library with no external dependencies.
-**Microsoft.Intune.MAM.SDK.aar*- contains both the interfaces necessary for enabling app protection policies and the code necessary to interoperate with the Microsoft Intune Company Portal app.
+**Microsoft.Intune.MAM.SDK.aar** contains both the interfaces necessary for enabling app protection policies and the code necessary to interoperate with the Microsoft Intune Company Portal app.
 
-**Microsoft.Intune.MAM.SDK.aar*- must be specified as an Android library reference:
+**Microsoft.Intune.MAM.SDK.aar** must be specified as an Android library reference:
 
  1. Open your app project in Android Studio and go to **File > New > New module**.
  2. Select **Import .JAR/.AAR Package**.
  3. Select Microsoft.Intune.MAM.SDK.aar to create a module for the *.AAR- file type.
- 4. Right-click the module or modules containing your app code and go to **Module Settings*- > **Dependencies tab*- > **+ icon*- > **Module dependency**.
+ 4. Right-click the module or modules containing your app code and go to **Module Settings** > **Dependencies tab** > **+ icon** > **Module dependency**.
  5. Select the MAM SDK AAR module you just created and select **OK**. This will ensure that your module compiles with the MAM SDK when you build your project.
 
 ### ProGuard
@@ -102,7 +102,7 @@ The SDK provides build tools (a plugin for Gradle builds and a command-line tool
 These tools transform the class files generated by Java compilation; they don't modify the original source code. 
 You're required to use either the Gradle plugin or command-line tool.
 
-**The build tooling alone is not sufficient to fully integrate your application.*- 
+**The build tooling alone is not sufficient to fully integrate your application.** 
 The tools perform [class and method replacements] only.
 They don't perform any more complex SDK integrations such as [Multi-Identity], [Registering for App Protection Policy], [Policy for limiting data transfer between apps and device or cloud storage locations], or [MSAL configuration], which must be completed before your app is fully Intune enabled.
 Carefully review the rest of this documentation for integration points relevant to your app.
@@ -171,10 +171,10 @@ The Gradle plugin has a dependency on [Javassist], which must be made available
 > [!NOTE]
 > Javassist versions may not be backwards compatible.
 > Generally, you should use the exact version expected by the MAM SDK:
->| MAM SDK Version | Javassist version |
->|-|-|
->| ≥ 7.0.0         | 3.27.0-GA |
->| < 7.0.0         | 3.22.0-GA |
+> | MAM SDK Version | Javassist version |
+> |-|-|
+> | ≥ 7.0.0         | 3.27.0-GA |
+> | < 7.0.0         | 3.22.0-GA |
 
 Additionally, when consuming MAM SDK 8.0.0+, you must ensure the following is set in your Gradle configuration:
 
@@ -326,8 +326,8 @@ This would have the following effects:
 
 - the `product-foo-project` directory is rewritten to `mam-build\product-foo-project`
 - `bar.jar` is rewritten to `mam-build\libs\bar.jar`
-- `zap.jar` is **not*- rewritten because it is only listed in `--classpath`
-- The `com.contoso.SplashActivity` class is **not*- rewritten even if it is in `--input`
+- `zap.jar` is **not** rewritten because it is only listed in `--classpath`
+- The `com.contoso.SplashActivity` class is **not** rewritten even if it is in `--input`
 
 > [!WARNING] 
 > The build tool does not currently support aar files.
@@ -336,7 +336,7 @@ This would have the following effects:
 ## Setting MAMApplication
 If your app creates a subclass of `android.app.Application`, then the build plugin / command line tool will transform your application class.
 
-If your app doesn't subclass `android.app.Application`, then you **must*- set `"com.microsoft.intune.mam.client.app.MAMApplication"` as the `"android:name"` attribute in your AndroidManifest.xml's `<application>` tag.
+If your app doesn't subclass `android.app.Application`, then you **must** set `"com.microsoft.intune.mam.client.app.MAMApplication"` as the `"android:name"` attribute in your AndroidManifest.xml's `<application>` tag.
 
 ## Recommended Android best practices