- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 04:02 AM
<Background>
I am currently verifying SAM Pro.
M365 integration is required, but verification will take time, so we will not introduce SAM Pro yet. Instead, we will manually create a Software Model (cmdb_software_product_model) and a Catalog Item (pc_software_cat_item) and start operation, and in parallel, we will verify SAM Pro and M365 integration, etc. separately.
<My understanding during verification>
As for the behavior of SAM Pro, I understand that "When you perform M365 integration, a Software Model is automatically created. Then, you can create a Catalog Item with one click from the related link of the Software Model."
*My understanding is that if you create a Catalog Item in this way, the Catalog Item name will be registered in the "Product Catalog" tab.
And if you install the separate com.snc.procurement plugin, you can assign to a user with the "sc_request > sc_task > Source Request" button, but I understand that the condition for linking the assignment is that the corresponding Catalog Item must be linked to the "Product Catalog" tab of the Software Model.
<Question>
I've made a long introduction, but if you manually create a Software Model and Catalog Item first, and then integrate with M365 and the Software Model is automatically created, of course you will use the automatically created Software Model in the future, but is there a way to link this automatically created Software Model with the manually created Software Model?
For example, when integrating with M365, you can customize it to link to an existing Software Model... (However, this is difficult, and I expect it is not recommended.)
Or would it be better to "not create the Software Model manually, but create only the Catalog Items manually and start operation, and then later integrate with M365 and automatically create the Software Model, and then set up the existing Catalog Items to be linked in the Product Catalog tab"? (The fields in the Product Catalog tab of the created Software Model are read-only, so we plan to link them using a script or something.)
The best practice would probably be to "create Catalog Items and start operation after M365 integration is complete," but since this is difficult as a customer request, I asked the above question.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 05:43 AM
You can configure the Software model now. Normalization can be implemented when you discover Software Models from M365
Palani
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 02:31 PM
Hi @nagaryu,
the table [samp_sw_subscription_product_definition] contains all SAM Pro subscription mapping between the portal subscription identifier and the software models (based on a DMAP). After running the first M365 import, SAM Pro will search for existing software models based on the linked DMAP to a) link the user subscription data with this model or b) create a new model to match the product definition.
To ensure that no new software models are created during M365 integration, it is recommended that the models be created based on the DMAP, as shown in the mapping table. Re-Linking the "subscription" software model with the existing one isn't recommended.
My preferred order for your case is:
Option 1) create models based on the mapping table & DMAP and link with cat item
Option 2) re-link catalog item & entitlements later with the M365 integration models
Option 3) do not create any model and use the cat item without it
Best, Dennis

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 04:09 AM
Hi,
If you use Normalize the Software Models, you will not face any issue. Refer the below links to know more details:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0859819
Palani
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 04:45 AM
Hi @palanikumar ,
Thank you for your quick reply.
So, can I understand that by using software normalization, the following can be achieved?
- First, create a software model manually.
- Next, correctly configure software normalization.
- Perform M365 integration.
- The information is correctly reflected in the manually created software model.
I have not yet learned much about software normalization, so I will take this opportunity to start learning more.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2025 05:43 AM
You can configure the Software model now. Normalization can be implemented when you discover Software Models from M365
Palani
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-08-2025 05:13 PM
Thank you for your reply.
I think the first thing I'll do is connect to M365, and then use normalization to link it to an existing Software Model.
I can't try it right now because I haven't set up an M365 testing environment yet, but I'll try again once I can use it. Thank you very much.