Microsoft Secure Tech Accelerator
Apr 03 2024, 07:00 AM - 11:00 AM (PDT)
Microsoft Tech Community
Understanding Unified Labeling migration
Published Aug 05 2019 12:43 AM 70.9K Views
Microsoft

This blog is updated for June 2020 and includes the latest Microsoft Information Protection capabilities that are now available.

 

TL; DR 

Unified labeling is here and it is the next step in the Microsoft Information Protection story. Each new Microsoft product and service that utilizes classification and protection capabilities (and 3rd party ones using MIP SDK capabilities) will require unified labeling. Because of this, now is the time to execute a migration to this service as there is zero risk when done properly following our recommended steps.

The primary migration plan is to migrate labels and policies from the Azure Information Protection blade in the Azure portal to the  Office 365 Security & Compliance Center, re-create your label conditions and deploy a Unified Labeling supported client, via an add-in or built-in Office 365 apps. Both can be deployed as a new installation or in-place upgrade to the Azure Information Protection client (classic). If you want to understand why this is necessary and why the migration plan is not as complicated as it initially sound, please continue to review the information contained in this blog.

Note: Unified labeling support is only available for commercial cloud tenants.

clipboard_image_0.png

 

Unified labeling Migration

Back in 2016 when the Azure Information Protection client was initially released, it was the first Microsoft product that introduced labeling capabilities which was applied on top of the already available Azure Rights Management service. The Azure Information Protection blade in the Azure portal replaced the old Azure Rights Management interface which was available only in the Azure classic portal.  At that point, Azure Information Protection was the only product that supported labeling of sensitive content as part of Microsoft portfolio.

 

Based on customer feedback and the evolution of Office 365, a strategic decision was made to integrate Azure Information Protection labeling capabilities into Office 365 services. Because the Office 365 suite of products were managed from the Office management portals and the plan included a big initiative to integrate Azure Information Protection labeling capabilities into Office 365 and many other Microsoft and 3rd party products, a unified approach has been agreed upon and initiated these changes:

  1. Microsoft introduced a unified SDK to be implemented by all applications and services that want to use Azure Information Protection classification and labeling – the Microsoft Information Protection SDK.
  2. A unified backend in the Office 365 eco-system to manage the Azure Information Protection labels – the Office 365 Security & Compliance Center (same label admin capabilities are also available at Microsoft 365 Security and Microsoft 365 Compliance portals).
  3. Referring to Azure Information Protection labels in a consistent and short name which will also differentiate from Retention labels that are already exist in Office 365 platformSensitivity labels.

Performing these changes caused the creation of a new label management tab, in addition to a new client support (via add-in and built-in Office 365 apps) that is based on the Microsoft Information Protection SDK. Unlocking the availability of Sensitivity labels across the complete Microsoft 365 platform.

 

At the time of writing this blog (Updated on November 2019), there are 2 main label management portals which are supported by different products:

(Note: To provide a unified and streamlined customer experience, the Azure Information Protection labeling ...)

  1. Azure Information Protection blade in the Azure portal - Supported by:
    1. The Azure Information Protection client (classic)
    2. The Azure Information Protection scanner (classic)
    3. Microsoft Cloud App Security
  2. Unified labeling console in Office 365 Security & Compliance Center – Supported by:
    1. The Azure Information Protection unified labeling client
    2. Microsoft Cloud App Security
    3. Azure Information Protection Scanner
    4. SharePoint Online
    5. Office 365 apps for Windows, MacOS, iOS and Android (built-in without an add-in requirement)
    6. Office for the web
    7. Outlook for the web
    8. Outlook for mobile devices (iOS & Android)
    9. PowerBI Data protection
    10. Microsoft Information Protection SDK and applications based on it (For example: Adobe Acrobat)

As you can see and understand, moving forward, every app and service that implement labeling capabilities in Microsoft will be using unified labeling exclusively. In addition to that, the Azure Information Protection client (classic) and portals are still here but not for long (a separate announcement will be published in the future and will details the specific plans).

 

Lastly, unified labels support advanced capabilities that aren’t available when Azure Information Protection labels are in use and are now available as part of the native integration with the Microsoft 365 platform. Some of these capabilities are:

  1. Enable sensitivity labels in Office 365 cross platform apps without deploying a client.
  2. Unified experience with applying sensitivity labels across Office 365 apps and services (built-in and with an add-in).
  3. Advanced label automation with the same logic as used by Office 365 DLP with sensitive information types, custom and pre-defined.
  4. Flexible label polices which now can scope the same label to multiple policies.

There is no risk for end users and production environment in migrating to unified labeling today, the migration process from Azure Information Protection backend to Security and Compliance backend is separated for labels and policies. So as long you didn’t publish a unified labeling policy or didn’t deployed an application that support unified labeling, nothing happens for end users and they still don't have the ability to apply sensitivity labels. 

Note that while enabling the migration doesn't change the label production capabilities till you publish a label policy. In case you have mails that are already labeled and sent internally, these labels will be visible in OWA.

 

So, what now? It’s time to migrate to unified labeling!

 

Are you a new customer who is just starting your Information Protection journey? Start with unified labeling and create your policies and labels in the Office 365 Security & Compliance Center (Or Microsoft 365 Compliance / Microsoft 365 Security portals in case you are a Microsoft 365 customer). New tenants are already enabled with unified labeling, so no action is required from your side. If no labels are already created and you wish to leverage Azure Information Protection default labels, go to the Azure Information Protection blade in the Azure portal and generate the default labels (Fig. 1). In addition, verify that your tenant is already migrated to unified labeling, if not, go to the unified labeling blade and activate the migration (Fig. 2). Once the service side configuration has be completed, continue to “Phase 3 – Client deployment” part of this blog to understand which client you should deploy so your users can leverage labeling capabilities in their environment.

 

Fig 1. Generate default labels

clipboard_image_1.png

Fig 2. Unified labeling migration activated

clipboard_image_0.png

Are you an existing Azure Information Protection customer who wish to migrate to unified labeling? Here are the suggested steps you should perform to plan and execute the migration:

 

Phase 1 – Planning

Unified labels support most functionalities that are available in Azure Information Protection labels, some functionalists are not available, and some are configured differently when managed from the Security & Compliance Center. There are also difference between which capabilities are available in each platform. Please review the following:

  1. Client differences between the classic client for Azure Information Protection, and the unified labeling client.
  2. How sensitivity labels work in Office apps, to learn about the built-in labeling capabilities, the supported environments and when they are available.
  3. Label settings that are not supported in the admin centers and learn how they are manageable.
  4. Features not planned to be in the Azure Information Protection unified labeling client. As a clarification please note that although custom permissions are not supported in the unified labeling client as a standalone action with the Office add-in, it is supported as a label that is configured with User Defined Permissions action.
  5. How you can use the AIP Unified Labeling client TODAY blog.

If one of the documented differences impact your end users behavior, please reflect this accordingly in your end user communication before deploying the latest client and publishing the unified labeling policy.

 

As of today (Updated on November 2019), the Azure Information Protection scanner and Analytics supports Unified Labels, are in preview and managed from the Azure Information Protection blade in the Azure Portal. Please note that Azure Information Protection Analytics - audit activities that are generated only form the Azure Information Protection client (Classic and Unified Labeling).

 

Phase 2 – Service migration

After you have reviewed the 1st phase, it’s time to migrate your labels and policies to the Security & Compliance Center. It is important to mention that “Migrate” doesn’t mean you need to move away from managing labels and policies in the Azure Information Protection blade and the Azure Information Protection client (classic). This migration can happen in the background and works side by side with no additional configuration.

 

Migration is a 2-step action:

  1. Enable label migration (Mandatory step).
  2. One-time policy copy from Azure Information Protection blade to Security & Compliance (Optional step).

Step 1: Label migration

We will start with describing what happens when you migrate your Azure Information Protection labels to unified labels. This happens once you click the “Activate” (Fig 3) button under “Unified Labeling” blade.  

Fig 3. Unified Labeling activation button for label migration

clipboard_image_2.png

Before you activate the migration, both Azure Information Protection backend and unified labeling backend are 2 separate services which work independently (Fig. 4). Once you activate the unified labeling migration, the labels are copied from the Azure Information Protection backend to the unified labeling backend and both services are using the same backend to store labels (Fig. 5). This means that every change you perform to any label at any portal will be changed also in the other portal.

 

Fig 4. Service architecture pre-unified labeling migration

clipboard_image_3.png

Fig 5. Service architecture post unified labeling migration

clipboard_image_4.png

After you activate the unified labeling migration, your labels are expected to be visible in both the Azure Information Protection blade and unified labeling page in the Security & Compliance Center (Fig 6).

Fig 6. Azure Information Protection and unified labeling in the Microsoft 365 compliance center post migration UI.

clipboard_image_3.png

Moving forward you can manage your labels at one place. After the migration, when you edit a migrated label in the Azure Information Protection blade, the same change is automatically reflected in the admin centers. However, when you edit a migrated label in the Security & Compliance Center, you must return to the Azure Information Protection blade, go to Azure Information Protection - Unified labeling blade, and select Publish. This additional action is needed for the Azure Information Protection clients (classic) to pick up the label changes. Once you are fully migrated to the unified labeling client, you no longer need to do this step, so migrating quickly helps to reduce this administrative overhead.

 

As you may notice, label configuration in the Security & Compliance Center doesn’t include some of the advanced settings that were able to be configured using Azure Information Protection labels. These configurations are now applied to the label after its initial creation / migration using the Security and Compliance PowerShell module. Here are few examples of these configurations:

A full list of all the advanced label settings is published here with instructions how to apply them. Please note that these label advanced settings are supported only by the Azure Information Protection unified labeling client on Windows and not by the Office 365 apps built-in integration with unified labeling.

 

Step 2: Copy policies

Once your labels have been migrated to Security & Compliance center we can discuss and check the possibility to migrate your policies as well with a one-time copy action (Fig 7.) Policies can be migrated or otherwise, you can create them manually and start this part from scratch.

 

Fig 7. Copy Policies (preview) button

clipboard_image_4.png

Selecting “Copy policies (preview)” will perform a one-time copy of your policies with their settings and any advanced client settings to the Security & Compliance center (Fig 8). Before doing that, there are few considerations that you should be aware of:

  1. Copy policy is being done for all policies that are configured in the Azure Information Protection blade.
  2. Once policies are being copied, they will automatically be published to all Unified Labeling supported clients. Please don’t copy your policies if you don’t want to publish them.
  3. To avoid duplications and conflicts, policies that are copied to Security & Compliance center naming convention is “AIP_<policyname>”. That mean that policies that are already configured in the same name in Unified Labels policy will be overridden (for example, you performed an update in Azure Information Protection policies and would like to update the policies in Security & Compliance, additional click on “copy policies” will update them).
  4. Due to different policy design, few advanced client settings are not copied in the process, these are “LabelbyCustomProperty” and “LabelToSMIME”.
  5. Unlike labels, copy policies doesn’t “synchronize” the policies between Security & Compliance center to the Azure Information Protection blade, once copied each platform policies is independent.
Fig 8. Copy policies summary after the action has been completed

clipboard_image_5.png

As an Azure Information Protection admin, you probably noticed that some policy configurations are not available when you configure your policy in the Security & Compliance Center. In case you copied your policies using the “Copy Policies” feature then these configurations are copied as well. For future policy configuration you will decide to use, or if you created your label policy manually, these configurations should be applied to the policy you created in the Security & Compliance Center after its initial creation and using the Security & Compliance PowerShell module. Here are few examples for such configurations:

The full list of all the advanced policy settings is published here with instructions for how to apply them. Please note that these advanced settings (both for policies and labels) are supported only by the Azure Information Protection unified labeling client and not by the Office 365 built-in integration with unified labeling.

 

Important Note: If you use Microsoft Cloud App Security and Azure Information Protection labels (or intend to do so in the future), verify you have published at least 1 policy with minimal set of labels even if this is scoped to a single user. This is required for Microsoft Cloud App Security to identify all labels in the Security & Compliance Center and show them in the Microsoft Cloud App Security portal.

 

What doesn’t migrate and need to be created separately?

  • Label conditions
  • Label translations

Why? As mentioned earlier in this blog, conditions are more flexible and have additional advanced settings that allows better accuracy and less false positive matches. Therefore, they cannot be directly translated across the services.

 

Label conditions should be created manually under each unified label as they are far more flexible than their Azure portal counterparts. By the way – If you already have custom sensitive information types that were built to use with Office 365 DLP or Microsoft Cloud App Security you can apply them as-is to a unified label with simple configuration. Read our official documentation on how to create automated and recommend rules for unified labeling.

 

Label translations can be configured, once labels are migrated, using Security & Compliance PowerShell module using the set-label cmdlet with the -LocaleSettings parameter. Please note that translations are supported only for labels and with the Azure Information Protection Unified Labeling client.

 

Phase 3 – Client deployment

The last part is to verify the end users will be able to get the unified labeling policies and labels. For this they need a supported client that knows to connect to the Security & Compliance backend and pull the unified labeling policy. For all non-windows platforms, there is no Azure Information Protection client as labeling capabilities are already integrated, out of the box in Office clients for MacOS, Office for the web (preview), Outlook Web App and Mobile devices. Once labels are published, these platforms will be able to leverage them. Click here to read how to apply sensitivity label in each platform that supports built-in labeling. For Windows platform there are 2 options you can use if you are using Office 365 ProPlus:

  1. Use Office 365 built-in label support (Versions newer them 1910 - 12130.20272)
  2. Deploy the Azure Information Protection Unified Labeling client

More details on the functionality differences are detailed in the official client comparison. What should lead you in the decision are the required functionality in the current point and time for your organization. As we move forward, more functionalities will be added to the built-in capability that doesn’t require an add-in to be deployed. Here is a short table that describe the major differences between these options:

clipboard_image_0.png

 

You can read more on the capabilities that are currently supported with Office 365 apps built-in labeling in this official documentation.

 

For Windows Office perpetual clients (2010, 2013, 2016, 2019), install the Azure Information Protection unified labeling client (Option 2) which can be downloaded from http://aka.ms/aipclient (verify you download the AzInfoProtection_ul.exe file. If you currently have Azure Information Protection client (classic) deployed, installing the unified labeling client will perform an in-place upgrade.

See the following screenshots (Fig. 9) that describe the experience across multiple platforms. You can also see this in the latest official documentation.

If you published your labels and the clients that have built-in support do not show the “Sensitivity” button, review the troubleshooting guide that covers this topic.

 

 
Fig 9. Consistent user experience for applying Sensitivity labels across different platforms.

clipboard_image_7.png

The main differences for end users who use the classic client for Azure Information Protection today and move to use the unified labeling client is the new “Sensitivity” button that replaces the “Protect” button (Fig. 10). The functionality and experience to apply labels remains the same with the vertical bar across all platforms and with the horizontal bar which is exclusive to the Azure Information Protection unified labeling client in Windows.

 

Fig. 10 – End users changes when upgrading from the classic client to the unified labeling client

clipboard_image_8.png

That’s it! Once you have performed the steps mentioned above, you have completed your migration to unified labeling and are now ready for the future and the exciting updates that will be available soon across the Microsoft 365 platform!

 

You can manage labels in one place which is the unified labeling console in Office 365 Security & Compliance Center. The only reason you may still need to use the Azure Portal for Azure Information Protection, is to manage the Azure Information Protection scanner and to monitor label activities using Azure Information Protection analytics.

 

If you have questions or want to follow up on the latest updates from Microsoft Information Protection, please review these resources:

32 Comments
Silver Contributor

Office Online is now just Office, or on the web :)

Bronze Contributor

Hi @Nir Hendler ,

what do I do with the Default MRM Policy in the EAC once we've migrated to the new Unified Labeling system?

We've never used the classic exchange retention policies. Do I just delete the policy in the EAC? Does that get rid of the Retention button in Outlook as well?

Microsoft

@Ivan Unger - Everything that was mentioned in this blog is not related to "Retention labels" and doesn't affect them. This refers to "Sensitivity" labels only,

Bronze Contributor

Am I understanding this correctly, that we (the user) are not supposed to label incoming emails, but only outgoing messages?

And therefore there is no way to retroactively apply a sensitivity label, like "personal" to a sent message?

Brass Contributor

@Nir HendlerIf I migrate my AIP labels to UL, and afterwards I apply advanced settings for the copied UL labels / Sensitivity labels using the PS SCC Module... will the labels keep the advanced configuration (e.g. colour settings) in UL even if I copy once again the labels from AIP to UL (e.g. because I create / change a label in AIP)? Or will it "overwrite" the advanced settings on the (existing) copied labels in the Security & Compliance Center?

 

Thanks in advance,

Martin

Microsoft

@MartinZoller - The enablement of Unified Labeling from Azure Information Protection blade is a one time action. The backend actions are described in the blog. From that point, both services (AIP and SCC) use the same label database and therefor, there is no option to "copy labels again" as they are connected. 

In Unified Labeling you need to distinguish between Policy advanced settings to Label advanced settings which have different concept then how they are configured in AIP labels. therefor, if a new label is created in AIP, you should add it's relevant advanced configuration using SCC PS.

We do recommend to manage your labels at one place after the migration, beside the scanner use case, there is no other reason to use both portals for label and policy management.

Brass Contributor

Why were the most highly used platforms left till last? How soon can we expect it to be available in office and SharePoint?

Microsoft

@Sam Gray Both platforms are expected to be available to the public by the end of CY2019. You can get more official updates in the Microsoft 365 roadmap page: https://www.microsoft.com/en-us/microsoft-365/roadmap?SilentAuth=1%26filters=

SharePoint integration is already in Private Preview.

Please note that these time frames (and ones the roadmap mention) can be considered only as estimations.

Copper Contributor

Any idea when this will roll out for GCC?  We were given the impression this was available back in March and had actually activated Unified Labeling for our GCC tenant.  We had successfully migrated our labels from AIP to the Security & Compliance center and were testing to see how we wanted to fully implement a labeling strategy when Unified Labeling was deactivated on our tenant without warning.  This led to multiple Premier Support tickets to finally be told yesterday that it's not available in GCC.

 

I checked the Microsoft 365 roadmap page but did not see anything related to Unified Labeling for GCC.

Microsoft

@Generik - This is a roadmap item with no ETA that can be shared at the moment.

Bronze Contributor

@Nir Hendler, thank you for the comprehensive information regarding the Unified Labeling migration. Very helpful. 

Copper Contributor

It looks like this work is really comming together. What I am missing as a big part of working with the documents and data is that the labels have to be able to Surface in SharePoint. I need to work with AIP labels as a metadatacolumn because I can't make everyone an admin. We need to be able to work with the labels in SharePoint (and OneDrive) to be able to sort, filter, set column formatting, Flow etc. 

Brass Contributor

Will AIP be removed from the EMS license then?

Microsoft

@Mike Crowley No there are currently no planned changes to Azure Information Protection licensing, meaning Azure Information Protection will continue to be part of EMS.

Brass Contributor

@Adam JungCan you expand on that? Is it just that you don't have "anything to share at this time" or that there is a continued reason a customer would want to buy AIP vs the unified labels?

Microsoft

@Mike Crowley we had a previous FAQ similar to this and pasted below. In short, you still need AIP licenses if you want to use the AIP client for downlevel versions of Office, to use the AIP scanner for on-premises files, etc. 

 

You still need Azure Information Protection P1/P2 for all the capabilities included in Azure Information Protection before the unified labeling experience was released (such as using the Azure Information Protection client, the Azure Information Protection scanner, etc.)To be able to configure sensitivity labels in the Security & Compliance center, you need either Azure Information Protection P1/P2 licenses OR Office 365 E3/E5 licenses (you don’t need both). Users do not need a license if their Azure Information Protection client (classic) is running in protection-only mode.

Brass Contributor

Thanks @Adam Jung , I had seen that before, but it seems like those are just "temporary problems" until everything is updated to support these new unified labels. Anyway, I'm not looking to split hairs here, so I'll just wait for future announcements.

Iron Contributor

Hi @Nir Hendler ...Is activation required in Azure portal even if AIP labels have never been used in a tenant? In our case, AIP default labels already exist but these have never been used so I am wondering if we simply create new labels in Security and Compliance center and not bother about any activation in Azure portal.

Microsoft

@Gurdev Singh - We recommend to enable UL migration in AIP portal so you can leverage these labels also for AIP Analytics and scanner.

Then both UL and AIP labels will share the same label store and will be aligned between them.

Iron Contributor

@Nir HendlerWe want to define DLP policies based on sensitivity labels e.g. display a policy tip in Outlook if user is sending a 'Top Secret' labelled document to external users. Is this possible? 

Microsoft

@Gurdev Singh - Integration between sensitivity labels and DLP rules is in our roadmap for later this year.

Iron Contributor

@Nir Hendlerthank you. Does sensitivity label work the same way as AIP labels in SharePoint search as outlined in this article? We have these configured in our environment but none of the labels are showing in crawled properties even after 2 days. Even if they did, would you recommend that approach. We have a project that would like to use sensitivity labels with policy tips and warning messages in email to train users initially but looks like DLP is lacking this feature currently.

Microsoft

@Gurdev Singh - The document you mentioned is not an official Microsoft document and therefor, I can't commit that what the described scenario is working today. As mentioned earlier, the only way for you to use Office 365 DLP with labels is to wait for this capability to be availble as an official solution.

That's even more specific to policy tips as in mail scenario, the label is usually applied after the mal is sent and on the service side, not before.

 

I recommend you to join the MIP Yammer community for any additional questions - https://www.yammer.com/askipteam/

Copper Contributor

Great article thanks @Nir Hendler 

I have a quick clarification question.

AIP label is applied to documents. We migrate. Some users have new clients and some do not. Does the original label appear applied correctly still for users in new clients under Sensitivity, and do both groups of users get to apply their respective labels (AIP/MIP) labels and both groups can see them?

Microsoft

@shaunhughes_im the label should remain the same post migration.

Copper Contributor

@Nir Hendler Hi man, Thanks for the nice post! 

I have some question about Microsoft Unified Labeling.

Is there any Yammer group for this kind of question? 

 

Otherwise I will ask my question here! 

Copper Contributor

Hello @Nir Hendler 

 

Thanks for the wonderful post. I have a question regarding the migration of AD RMS to AIP. We are planning to do it via DNS redirect option. At the same time, we are upgrading our AIP clients to Unified labeling clients. 

 

Now can I modify the SRV record to point AD RMS URL to AIP tenant or is there any specific URL for Security and Compliance center?

 

Thanks in Advance

 

-Ram

Microsoft

@Ramkumar495 Please post your question at the Ask MIP Yammer community - https://www.yammer.com/askipteam/

Brass Contributor

@Nir Hendler Thank you very much for sharing such a valuable post.  One question I would like to clarify with you, When we Intergaret AIP UL with Azure Sentinel the Sentinel captures audit activities that are generated only from the Azure Information Protection client or will it capture Office-app built-in label activities and SharePoint Online/ Ondrive for business classification activities as well? 

Also would appreciate if you can share more information about AIP UL and Azure Sentinet integration. 

Thanks. 

Microsoft

@Nip17 Today these logs include AIP Client activity. In the future, built-in labeling will be included as well

Brass Contributor

Thanks @Nir Hendler 

 

I have a requirement to migrate 13K+  user based from AIP classic to  AIP UL, Auto classification, and trainable classifier. They are heavily using AIP with custom regex and AIP scanner as well. 

The planning step is ok, but I have a few questions on the migration step. 

 

  1. Enable label migration- once we enabled this on AIP azure portal all labels get created in SCC. 

       Q1.1- Does it means users can still continue to use AIP classic client until we publish UL labels in SCC?

 

      2. One-time policy copy from Azure Information Protection blade to Security & Compliance 

       Q2.1- After we copied policies can users still continue to use AIP classic client until we publish the policies in SCC?

       Q2.2- When we publish the copied policies to a pilot group from SCC, will it affect the users who are still using the classic AIP on windows, Andriod and IOS? 

       Q2.3- When classified documents shared within the organization, Can pilot users (who have Ul client installed)  open the documents classified with AIP classic, and can other users who are having AIP classic client installed can open the documents classified with UL labels? What would be the expected behavior for emails in this situation? 

       Q2.4- What will happen to the custom regex they have already use in AIP classic, can we still use those regexes directly in AIP UL. 

      3. Currently AIP scanner is using classic labels and classic client, how these labels and policy migration affect the AIP scanner? can we still continue to use AIP scanner until we test with the pilot users?

      4. Auto classification for SharePoint and Onedrive for business, I know for all contributors required E5 license, but we have guest (B2B) users who have contributor access to a couple of our SharePoint sites, so does it means we have to assign E5 license for them from our tenancy to work Auto classification for the document that they create? 

     5. What is the license requirement for the trainable classifier, I hope it will be the same required as Auto classification? 

     6. Any additional advice from you? 

 

Realy sorry about asking a lot from you.  Much appreciate your advice and answers.

 

Thanks. 

Microsoft

@Nip17 - As this article is not the proper place for such deep discussions. Please post such questions at the Ask MIP Yammer community: https://www.yammer.com/askipteam

Co-Authors
Version history
Last update:
‎Jun 11 2021 10:44 AM
Updated by: