[Magisk] amw2320:
Block the subprocess fix?

I may have found a fix using the same solution as the pokemon go guys.

Adding a series of subprocesses which are loaded during the compliance check to magisk hide seems to do the trick.

magiskhide --add com.microsoft.windowsintune.companyportal:auth
magiskhide --add com.microsoft.windowsintune.companyportal:omadm_client_process
magiskhide --add com.microsoft.windowsintune.companyportal:fencing_client_process

I am now passing the compliance check when run manually through the app. This hasn't been running long enough to make sure background checks are caught, but I'll update if it gets flagged.

Note that I just blanket blocked everything instead of trying to figure out the exact subprocess or subprocesses that need to be blocked.

You can see in the logcat below that Magisk pops in as each of the processes are loaded

Logcat (filtered by string 'company')

marlin:/ $ logcat | grep company
04-11 10:44:32.464 882 4410 I ActivityManager: Start proc 6343:com.microsoft.windowsintune.companyportal:omadm_client_process/u0a181 for content provider com.microsoft.windowsintune.companyportal/com.microsoft.omadm.apppolicy.AppPolicyContentProvider
04-11 10:44:32.469 477 638 I Magisk : proc_monitor: com.microsoft.windowsintune.companyportal:omadm_client_process (PID=6343 ns=mnt:[4026534462])
04-11 10:44:32.661 6343 6343 I AndroidInsanity: Content provider attached: [com.microsoft.windowsintune.companyportal.powerlift.provider]
04-11 10:44:32.774 6343 6343 I com.microsoft.omadm: Initializing logging to file pattern: /data/user/0/com.microsoft.windowsintune.companyportal/files/OMADMLog_%g.log
04-11 10:44:32.812 6343 6343 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:44:33.862 6343 6343 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:44:34.948 6343 6343 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:44:35.307 6300 6300 I MAMComponents: Initializing MAM classes with the MDM package: com.microsoft.windowsintune.companyportal
04-11 10:44:41.232 6479 6479 I MAMComponents: Initializing MAM classes with the MDM package: com.microsoft.windowsintune.companyportal
04-11 10:44:43.189 6515 6515 I MAMComponents: Initializing MAM classes with the MDM package: com.microsoft.windowsintune.companyportal
04-11 10:44:45.210 6563 6563 I MAMComponents: Initializing MAM classes with the MDM package: com.microsoft.windowsintune.companyportal
04-11 10:44:56.539 882 1238 I ActivityManager: Start proc 6897:com.microsoft.windowsintune.companyportal:fencing_client_process/u0a181 for service com.microsoft.windowsintune.companyportal/com.microsoft.intune.fencing.client.FencingClientService
04-11 10:44:56.544 477 638 I Magisk : proc_monitor: com.microsoft.windowsintune.companyportal:fencing_client_process (PID=6897 ns=mnt:[4026534452])
04-11 10:44:56.826 6897 6897 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:45:16.865 882 1238 I ActivityManager: Killing 6897:com.microsoft.windowsintune.companyportal:fencing_client_process/u0a181 (adj 906): empty #17
04-11 10:45:19.211 882 4410 I ActivityManager: Killing 6343:com.microsoft.windowsintune.companyportal:omadm_client_process/u0a181 (adj 906): empty #17
04-11 10:46:06.395 882 2355 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.microsoft.windowsintune.companyportal/.views.SplashActivity bnds=[1123,337][1393,686]} from uid 10032
04-11 10:46:06.440 882 1238 I ActivityManager: Start proc 10154:com.microsoft.windowsintune.companyportal/u0a181 for activity com.microsoft.windowsintune.companyportal/.views.SplashActivity
04-11 10:46:06.456 477 638 I Magisk : proc_monitor: com.microsoft.windowsintune.companyportal (PID=10154 ns=mnt:[4026534473])
04-11 10:46:06.592 10154 10154 I FA : adb shell setprop debug.firebase.analytics.app com.microsoft.windowsintune.companyportal
04-11 10:46:06.622 882 909 I ActivityManager: Start proc 10173:com.microsoft.windowsintune.companyportal:omadm_client_process/u0a181 for content provider com.microsoft.windowsintune.companyportal/com.microsoft.intune.common.settings.PreferencesContentProvider
04-11 10:46:06.623 477 638 I Magisk : proc_monitor: com.microsoft.windowsintune.companyportal:omadm_client_process (PID=10173 ns=mnt:[4026534498])
04-11 10:46:06.697 10173 10173 I AndroidInsanity: Content provider attached: [com.microsoft.windowsintune.companyportal.powerlift.provider]
04-11 10:46:06.734 10173 10173 I com.microsoft.omadm: Initializing logging to file pattern: /data/user/0/com.microsoft.windowsintune.companyportal/files/OMADMLog_%g.log
04-11 10:46:06.736 10173 10173 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:46:06.954 10173 10173 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:46:07.215 10173 10173 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:46:07.217 10154 10154 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:46:08.012 882 909 I ActivityManager: START u0 {flg=0x10000000 cmp=com.microsoft.windowsintune.companyportal/.views.CompanyAccessNavigatorActivity} from uid 10181
04-11 10:46:08.065 882 2355 I ActivityManager: START u0 {cmp=com.microsoft.windowsintune.companyportal/.views.AadAuthenticationActivity (has extras)} from uid 10181
04-11 10:46:08.242 882 941 I ActivityManager: Displayed com.microsoft.windowsintune.companyportal/.views.AadAuthenticationActivity: +153ms (total +1s806ms)
04-11 10:46:12.467 882 909 I ActivityManager: START u0 {flg=0x10000000 cmp=com.microsoft.windowsintune.companyportal/.views.MainActivity} from uid 10181
04-11 10:46:12.745 882 941 I ActivityManager: Displayed com.microsoft.windowsintune.companyportal/.views.MainActivity: +250ms
04-11 10:46:12.870 882 909 I ActivityManager: Start proc 10298:com.microsoft.windowsintune.companyportal:auth/u0a181 for service com.microsoft.windowsintune.companyportal/com.microsoft.workaccount.authenticatorservice.AuthenticatorService
04-11 10:46:12.873 477 638 I Magisk : proc_monitor: com.microsoft.windowsintune.companyportal:auth (PID=10298 ns=mnt:[4026534410])
04-11 10:46:12.932 10298 10298 I DeploymentSettings: Loading settings file from /data/user/0/com.microsoft.windowsintune.companyportal/files/settings.xml failed because it probably wasnt created yet. Loading the settings file from the application binary resources instead.
04-11 10:46:37.751 882 1516 I ActivityManager: START u0 {cmp=com.microsoft.windowsintune.companyportal/.views.DeviceDetailsActivity (has extras)} from uid 10181
04-11 10:46:37.886 882 941 I ActivityManager: Displayed com.microsoft.windowsintune.companyportal/.views.DeviceDetailsActivity: +117ms (total +15s205ms)
04-11 10:46:40.762 882 1516 W ActivityManager: Unable to start service Intent { act=com.google.firebase.MESSAGING_EVENT pkg=com.microsoft.windowsintune.companyportal } U=0: not found
04-11 10:47:10.171 10714 10714 I MAMComponents: Initializing MAM classes with the MDM package: com.microsoft.windowsintune.companyportal
04-11 10:47:11.257 10752 10752 I MAMComponents: Initializing MAM classes with the MDM package: com.microsoft.windowsintune.companyportal
04-11 10:47:12.375 10787 10787 I MAMComponents: Initializing MAM classes with the MDM package: com.microsoft.windowsintune.companyportal