Copy-paste issue (COPE)

Simon
Level 2.0: Eclair

Hello Everyone,

I have a slight issue with copy-paste on Corporate owned, personal enabled devices (COPE) managed via Intune. To put it simple - people can copy text from work profile to personal. Happy to be pointed to the basics if I missed something obvious, but I feel stuck.

Intune configuration for COPE devices has 2 values: "allow" or "not configured" (not helpful). I had support cases open with Microsoft and Samsung, but former blames OS defaults, while latter blames Intune (not helpful).

I couldn't identify the setting in OEMConfig (Knox Service Plugin), so got Google Enterprise account, configured it for Zero Touch enrolment using Intune token and realised that I was looking into "crossProfileCopyPaste" control and don't have a clue how to use it in DPC extras and if that's even possible.

Is it possible to use AMAPI with Intune management? If yes, does anyone have any examples? What are other ways to restrict copy-paste from work profile to personal? I find it difficult to believe I'm the only one having the issue.

Thank you in advance

29 REPLIES 29

JacS
Level 1.5: Cupcake

Hi there,

It sounds like you're facing a tricky situation with managing copy-paste between work and personal profiles on COPE devices. You've already done a lot of groundwork by exploring Intune settings, OEMConfig, and even delving into Google Enterprise solutions.

Regarding your question, AMAPI (Android Management API) can indeed be used to enforce stricter policies, but integrating it with Intune might not be straightforward, as Intune generally abstracts a lot of the lower-level controls that AMAPI provides.

For crossProfileCopyPaste, while it's possible to control this through DPC extras in a pure Android Enterprise setup, doing so within the confines of Intune can be challenging, especially since Intune's configuration options may not expose all the granular controls you need.

You might want to consider setting up a custom policy using Intune’s Device Configuration Profiles, where you can explicitly block copy-paste actions via App Protection Policies. This might not directly expose crossProfileCopyPaste but could achieve a similar effect by limiting data sharing between work and personal profiles.

Additionally, you could explore Samsung Knox's advanced settings in more detail, as Knox provides more granular controls over work profiles that could complement what Intune offers. Combining Knox with Intune might give you the additional layers of security you're looking for.

I hope this helps, and feel free to reach out if you have more questions!

 

Simon
Level 2.0: Eclair

Thanks all for your input. I'm being vague intentionally (NDA), but this is now being looked into and should be fixed.

 

Sharing workaround if someone else runs into this before resolution:

Create a new device restriction policy

Set copy/ paste to Allow and save

Reset copy/paste to Not configured and save.

Please note workaround doesn't work for existing policies, you need to create a new policy

Glad to stumble upon this thread and see that I'm not the only one experiencing this. Annoying because it had previously worked, and I only discovered it while migrating devices to a newer configuration profile. (Side note, it is ridiculously frustrating how Microsoft makes us create whole new profiles to get access to newer settings instead of updating existing to new templates, but I digress.)

 

If I understand correctly, it sounds like Microsoft is working on a fix? Any chance they gave an idea of WHEN it will be fixed that you can share?

I don't have the full picture, so please take this with the pinch of salt.

The way I was explained, it's not Microsoft fixing things this time, and it should be fixed "beginning of August".

Being sarcastic - nobody said which year, but I'm happy there's a workaround 🙂

That makes me think perhaps it's more of an Android issue, so maybe with the updates for Device Policy app or Android monthly updates, etc. Either way, that's great to hear some idea of time around it. Here's hoping they do mean August 2024, lol.

Simon
Level 2.0: Eclair

Hopefully we're talking about the same thing:

 

{
"mCategoryMap": {
"RCP_CATEGORY": {
"mKeyMap": {
"poRCPMoveFilesFromWorkProfileToPersonal": {
"mData": null,
"mMessage": "[Allow moving files from work profile to personal space in Work profile policies (Profile Owner) successfully processed.]",
"mPolicyStatus": true,
"mReportStatus": 1
},
"poRCPMoveFilesFromPersonalToWorkProfile": {
"mData": null,
"mMessage": null,
"mPolicyStatus": false,
"mReportStatus": 0
},
"poRCPShareClipboardToData": {
"mData": null,
"mMessage": "[Enable Sharing of Clipboard Data to Owner in Work profile policies (Profile Owner) successfully processed.]",
"mPolicyStatus": true,
"mReportStatus": 1
},
"poRCPDataSyncPolicy": {
"mData": null,
"mMessage": "[Enable RCP data sync policy (Configure profiles below) in Work profile policies (Profile Owner) is not supported by this device.][14001][This policy is not supported for this knox version or higher.]",
"mPolicyStatus": true,
"mReportStatus": 1
}
}
},
"CMFA_CATEGORY": {
"mKeyMap": {}
},
"KPU_CATEGORY": {
"mKeyMap": {
"profileName": {
"mData": null,
"mMessage": "Knox policies in EMEA_v1.34 successfully processed",
"mPolicyStatus": true,
"mReportStatus": 1
},
"kpePremiumLicenseKey": {
"mData": null,
"mMessage": "Successfully activated license key ending with ...PNJZ",
"mPolicyStatus": true,
"mReportStatus": 1
}
}
}
},
"mStatus": "SUCCESS",
"mTimeStamp": 1721038679013
}

Michel
Level 2.2: Froyo

That looks like the one I was looking for but it seems to be lacking some information. 

 

Couple of things that I see in this config (you might have configured it but did not copy it to your post):

  • No license key - You need a KPE license (free) at least (RCP is marked as a premium function which used to be a paid license)
  • The policy to allow files from work to personal (first one in the code) appears to be set to true, while you had it set to false in the screenshot you shared earlier. 
  • Same for clipboard data
  • The RCP function is indeed not needed here, you don't need to set it to true of false. 
  • The section above the RCP policies is not enabled ( Work profile polices (Profile Owner) -> Set Enable work profile policies to true). 

 

I tried to replicate the issue you are experiencing since I don't understand why it should not work. But with all the settings mentioned in this topic, I was still able to copy paste from work to personal. Since I had to get back to work, I moved my user account of my demo device back to its original group I use for trainings and that group seems to have a policy, or a mix of policies, that solved it. 

 

I'm not able to copy paste form work to personal, and i'm not able to move files from work to personal. But I am able to copy paste to my work profile and share files with work profile apps. 

 

I will share the config below and leave it up to you to figure out what works for you, since I really have to get back to my work 😂

 

Knox Service plugin. (with a free Knox platform for Enterprise license key)

Michel_0-1721122273632.png

 

 

And the Intune - Android Enterprise restrictions profile:

Michel_1-1721122199837.png

 

 

Good luck and please let me know what did the trick if you find out! 

Moombas
Level 4.1: Jelly Bean

Reg. license key: he did copy this:

 

"kpePremiumLicenseKey": {
"mData": null,
"mMessage": "Successfully activated license key ending with ...PNJZ",
"mPolicyStatus": true,
"mReportStatus": 1

 

Which means a license key is there.

Michel
Level 2.2: Froyo

You are correct, missed that one! Thanks for checking. 

Simon
Level 2.0: Eclair

Please don't apologise that you need to get back to work, I appreciate your time and effort and have no expectations you have a solution. The purpose of posting here is to get ideas/ suggestions, which hopefully would lead to a solution.

Re report (export), I don't know how things should be represented, but Intune still shows values as per my screenshot. At this point I can't compare it against anything else as I don't have a "working" solution.

Re "Set Enable work profile policies" it's probably not represented in the log as without it other policies are not processed and I get some errors in KSP.

Thanks for the screenshots. What I find interesting, that you profile doesn't appear to have "Allow moving files from work profile to personal space" configured.

Either way I fully replicated the settings you shared (OEMConfig + restriction profile) and can still copy-paste text from work to personal profile 😖

The only 3 theories I have at the moment:

  • Microsoft updated Intune "templates" and newly created policies behave differently from the older ones, this would explain why you couldn't restrict data leak with the new profile, but I understand it's at a conspiracy level theory
  • The tenant configuration is different - over a year ago we had an issue where available apps were missing in the store and the fix applied by Microsoft was to migrate our tenant to the new Android API (whatever that means)
  • There's a setting outside the areas I'm looking into

The dream continues

Michel
Level 2.2: Froyo

@Simon wrote:

 

Thanks for the screenshots. What I find interesting, that you profile doesn't appear to have "Allow moving files from work profile to personal space" configured.

 


Thats what i found very strange as well, but it did the trick on multiple devices. And there are no other policies assigned to those devices. 

 

Are you sure there is no conflict somewhere with another policy? And getting back to basics: Are you sure you are not enrolling as BYOD / personal device? (Its probably correct but still, might worth to check again). 

 

I like your theories, I know that some MDM solutions required migrating to new policies after a big change in Android about two years ago (can't remember the exact reason). This had to do with some backend settings that they didn't want to mess with so they kept the original and asked you to migrate to new profiles which had the same settings but where different in the backend of the MDM solution. So that might very well be the case. Did you try this all with fresh / new policies or did you edit an existing one? 

 

In Intune there are a lot of areas to cover, but for Android it shouldn't be that difficult: 

  • Your configuration policies
  • Your Samsung Knox Service plugin OEM config
  • Your app configurations
  • Enrollment profiles and restrictions. 

 

Just out of my head, these are the ones you need. What did MS support suggested regarding this? 

Simon
Level 2.0: Eclair

Re conflicts, I can't see any conflicts in Intune. Single configuration profile assigned to the device according to Intune device properties page, KSP is not in production and there's only one configuration in the tenant (testing), app configurations excluded for testing, enrolment restrictions do exist, but they're blocking old OS versions, enrolment itself does succeed. So pretty sure there are no conflicts.

Devices appear as Android Enterprise (not Android for work) in Intune, ownership is corporate. We enrol them via QR code or Android Zero touch (details uploaded to Google by reseller), so they're enrolled as expected as much as I know.

Microsoft support was... doing their thing. Explained that setting is "Not configured", so they don't control the setting and I need to speak with the phone manufacturer re "OS defaults". When I asked how I can prevent the data leak, I was told to use applications which can be protected via Application Protection Policy (Intune App SDK) and if apps I need don't support that, I need to speak with software developers so their apps are compatible with Intune Application Protection Policies. In a nutshell - it's not our problem until you prove it's our problem.

Michel
Level 2.2: Froyo

Well, thats a very helpful answer from MS. 😑

 

I'm running out of ideas, sorry! When I have the change is will see if I can find what is working for me. Its the most basic Intune environment there is, so it should not be that hard to see why its working for me. 

 

If I find something or come up with another suggestion, I will let you know! 

Michel
Level 2.2: Froyo

Did you try the option "Data sharing between work and personal profiles"  in Intune? You can find it in the restrictions profiles under general settings. 

 

Michel_0-1720422861820.png

 

I have no test devices in Intune at the moment, but I believe this should do the trick. 

 

In KSP you have an option to allow clipboard sharing between work container en personal profile, but this is disabled by default:

 

Michel_1-1720422994902.png

 

Simon
Level 2.0: Eclair

Thanks for your response. That Intune setting is for file access only. It restricts accessing files from personal profile, which in my world is part of the job. Re text copy-paste Intune has another:

Simon_0-1720424910470.png

What's worse, is that if policy is created for BYOD and not COPE, the settings are "Block" and "Not configured".

 

I did set the KSP setting you mentioned to "false", but it had no effect in my scenario. The documentation I found implies it's to do with clipboard sharing between the devices. Not bothered about that currently 😊

 

I strongly believe I need to find a way how to control CrossProfileCopyPaste setting:

https://developers.google.com/android/management/reference/rest/v1/enterprises.policies#crossprofile...

Michel
Level 2.2: Froyo

ah okay, i understand!

 

Just to be sure: You want to block copy and paste from work to personal, but keep the option to transer files from work to personal?

 

 

Simon
Level 2.0: Eclair

The goal is to block copy-paste from work to personal profile (text and files), but leave the option to copy-paste from personal to work profile (text and files). In a nutshell, data transfer is possible only one way

Michel
Level 2.2: Froyo

I just tested the policies mentioned by @Moombas , and it seems to do exactly what you want. When set up like shown in the picture below, i'm unable to copy and paste text or files from work to personal while still being able copy from personal to work. 

 

Michel_0-1720445481780.png

 

This can be configured within the KSP plugin, the screenshot is from Knox Manage but it shows the KSP part which works the same for both. 

  1. Set Enable work profile policies to true
  2. Find RCP policy (premium function, you need the free KPE licenses from your knox tenant)
  3. Set as shown in above picture.  

Simon
Level 2.0: Eclair

Thanks for testing. I would say I have the same config:

Simon_1-1720448369678.png

KSP has no errors on the phone, displays new profile name and all the settings, but I still can launch Chrome in work profile, copy text and paste into any app in the personal profile.

Michel
Level 2.2: Froyo

Did you enter a KPE license? You need to generate one and then add it to KSP. Knox Platform for Enterprise licenses | Knox Platform for Enterprise | Samsung Knox Documentation

 

And, not sure, you might need to enable "Device-wide policies (Selectively applicable to Fully Manage Device (DO) or Work Profile-on company owned devices (WP-C) mode as noted)" as well. I've had some strange issues before when I had this part not enabled. 

 

I've been told that it activates some aspects that are also needed by the work profile policies (someone didn't think this one trough I think 😅)

Simon
Level 2.0: Eclair

The license is there (deleted it in the screenshot). KSP on the device displays message "Successfully activated license key ending with..." So I ruled license issues out


Added additional setting as per your message:

Simon_0-1720451657879.png

Still the same experience - can copy text from work profile apps.

Would be funny if it wasn't sad 😑

Michel
Level 2.2: Froyo

Very strange. A support case with Samsung might help as Moombas suggested. Just to be sure, you have pushed the KSP app as well?

Simon
Level 2.0: Eclair

The case with Samsung is open for a while now, but it's not looking promising. I was told "we're limited to what we can do in Intune"
KSP app has debug mode enabled. The app is installed, Knox license is accepted, profile name (version) match what I see in Intune.

The only setting which is not supported is "Enable RPC data sync policy (Configure profiles below)" with the following message "This policy is not supported for this knox version or higher". Not too worried as according to Samsung's documentation it's not supported from Knox 3.8.0 and phone is on 3.10.0

Michel
Level 2.2: Froyo

Do you mind sharing the xml export from the debug mode?