Cloud Discovery Not Updating Certain CMDB Attributes. Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The cloud discovery process is not populating several attributes in the CMDB, including Environment, Location, 'Managed by', 'Managed by Group', Serial number, Model ID, Manufacturer, Category, IP address, Operational status, Hostname, Class, and Natted IP. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } NA Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Environment :a. OOB Discovery does not populate the Environment field, because discovery does not know which environment the CI belong to.b. This field has choices for which you can update the field manually in the CMDB.c. You can also add a business rule to populate the environment field. Please note this will be considered as customization.Please refer to the the below SN community articles for more information.https://www.servicenow.com/community/itom-forum/best-way-to-update-the-environment-in-the-cmdb-cis/m-p/9484262. Location : This field is not directly populated by Discovery; however, when a discovery schedule is used, the Location field of the CI will be set based on the Location defined in that schedule.https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB08641143. The "Managed by" and "Managed by Group" fields are part of the CSDM framework and are not auto-populated by Cloud Discovery; they are intended to be set by users according to their business requirements/ Services, reflecting the ownership and responsible group for managing the respective CIs.Please refer : https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/csdm-implementation/concept/csdm-data-synchronize.htmlhttps://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/csdm-implementation/task/csdm-data-synchronize-enable.htmlhttps://www.servicenow.com/community/itom-forum/cmdb-owned-by-and-managed-by-definitions/m-p/923987YouTube : https://www.youtube.com/watch?v=MECwnUCf6ac&list=PLkGSnjw5y2U7QNr9jL6TAgwQvYBI_LEtK4. Serial number, Model ID, Manufacturer, Category, IP address, Operational status, Hostname, Class, Natted IP :These fields are not populated by default in cloud-based discoveries. This is because these are virtual resources, not physical hardware, so attributes like these there at all or exposed by cloud providers.All of these depend from cloud to cloud and resource to resource; you may refer to the product documentation and check the "Data Collected" section—if the above fields are not part of it, they will not be populated. This behavior is expected.Please review below doc: Data collected - Sectionhttps://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/discovery/reference/data-collected-azure-discovery.htmlhttps://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/discovery/reference/cloud-disco-aws-data-collected.htmlhttps://www.servicenow.com/docs/bundle/zurich-it-operations-management/page/product/discovery/reference/data-collected-gcp-discovery.html