Reconciling Office 365 E3 subscription data with Microsoft 365 E3 entitlement

Tim18
Tera Contributor

Hi,

I was wondering whether anyone has come across/have the solution to how I can reconcile Office 365 E3 usage (coming from the Office 365 integration) with entitlement for Microsoft 365 E3? 

Office 365 E3 is essentially a component of M365 E3, although I don't believe that is contractually recognised in the respective licensing. https://www.microsoft.com/en-gb/microsoft-365/enterprise/compare-microsoft-365-and-office-365. I was hoping that I could get around it by setting Office 365 E3 as a suite component, but that does't get applied in the reconciliation results - presumably because subscriptions don't have the concept of suites.

Plan B is to ask our ServiceNow admins to setup a script to transform the Office 365 E3 subscription data when it comes in to M365 E3 so we can reconcile it. However that feels like it should be a last resort so wanted to check here first.

Many thanks

1 ACCEPTED SOLUTION

rohantyagi
ServiceNow Employee
ServiceNow Employee

Hi Tim,

We are developing the solution to reconcile Microsoft 365 components like Office 365, windows10 and EMS into one Microsoft 365 software. [Under Servicenow standard safe harbor] This will be available in the Quebec release. However we are also considering backporting it to older releases, i will be able to give you more information on the timelines or patch number in the next 3-4 weeks. Please tag me in the comment if you don't hear back. 

 

I am also happy to show you how this is going to work in one of our development environments. If interested, please send me an email at rohan.tyagi@servicenow.com

 

Regards,

_Rohan

View solution in original post

11 REPLIES 11

We've been struggling with this. It hasn't been back-ported to Paris. One of my other customers is using Quebec and the solution Rohan outlines precludes the need to mess around with the suite components and inference percentages for O365, EMS and W10. 

That said, I think there is a much-needed whitepaper that discusses the best practice for managing suites. I've said it before and I'll say it again: getting the correct results when reconciling suites appears to be trial and error based on the suite components, mandatory products and inference percentages. It shouldn't be like this.

Rohan, any update on this?
We are struggling with reporting usage for the web based Office suite for our M365 subscriptions. The O365 integration seems to ignore these and only reports for products like Yammer, Teams, Visio etc but no Office Suite of products. Also, the integration does not populate anything in the samp_sw_o365_usage_report table. Is that normal with M365 Subscriptions?

Our customer wants to be able to see which online apps are being accessed (last_activity) in the subscription table (samp_sw_subscription).

If this is not possible, are we able to allocate local desktop Office suite installations against our M365 entitlements? Does reconciliation account for that along with showing usage somehow? I'm guessing that comes from SCCM?

 

Thanks,

Darren

@rohantyagi Is this solution developed? Windows 10 and similar components are not part of M365 suite component. We need to manually configure suite for each model under M365. This can mess up the OOB functionality in ServiceNow. 

Anwer
Tera Contributor

Is there an update for this issue? We are on Tokyo and even when integrating to the Microsoft Portal we are seeing all components separately broken out instead of a suite of products for M365 (office apps, win 10, ems)

Hong Ngoc Trinh
Tera Contributor

Is there any update for this issue? We are on Utah and also struggling with this, instead of a suite of product for Microsoft 365, the components are broken out. Please advise the solution.