public preview
3 TopicsExtending Sentinel Data Integration: Azure Blob Storage Support for CCF Connectors
As organizations scale their security operations, the ability to ingest, process, and analyze high volumes of data reliably becomes increasingly critical. Microsoft Sentinel continues to expand its ecosystem through the Codeless Connector Framework (CCF), enabling ISVs to build and deliver integrations with Sentinel faster while simplifying deployment for customers. Today, CCF extends even further with support for Azure Blob Storage, introducing a new pattern for how data can be delivered into Sentinel. Expanding Connector Patterns with Azure Blob Storage CCF has traditionally enabled connectors that integrate directly with partner APIs and data sources. With this latest enhancement, ISVs can now build connectors that read data from Azure Blob Storage—unlocking new flexibility in how security data is collected and delivered. In this model, an ISV writes data to an Azure Blob Storage account. The Sentinel connector then reads from that storage layer, using Azure-native components such as Event Grid and storage queues to process events and forward them through data collection rules (DCR) into Log Analytics workspace. This approach introduces a durable data layer between the data source and Sentinel, enabling more resilient and scalable ingestion scenarios. Read the full announcement here: Extending Sentinel Data Integration: Azure Blob Storage Support for CCF Connectors Original Publication: Microsoft Sentinel Blog, May 5th, 2026178Views0likes0CommentsAnother Microsoft Places Upload Error
After setting up Microsoft places I have a part (one floor) of our building made in imdf format to upload to microsoft places, I made the correlation file PS C:\Windows\System32> Import-MapCorrelations -MapFilePath "c:\temp\imdf_map.zip" -CorrelationsFilePath "c:\temp\mapfeatures.csv" INFO: Correlations file c:\temp\mapfeatures.csv was provided. Adding the Places Directory Ids to the map data according to the correlations file... INFO: No custom output file name provided, will write to imdf_correlated.zip. INFO: Updated 3 features in the map files. SUCCESS: correlated IMDF zip package created and ready to import into Places! Looks like the correct correlations where made, but after creating the map I get the following error: PS C:\Windows\System32> new-map -BuildingId xxxxxxxxxx-xxx-xxxx-xxxx-xxxxxxxxx -FilePath "C:\temp\IMDF_correlated.zip" New-Map: Status(StatusCode="Internal", Detail="ErrorInvalidOrgPartition") Can't find any error details on this error, what I am doing wrong... Anybody suggestions?Solved453Views0likes1CommentMicrosoft Places Upload Errors
I am configuring the public preview of Microsoft Places with a client and when we tried to upload the IMDF files after uploading the building/floors CSV, the following error message appeared in the shell: "Import not supported for file fixtures.geojson" We removed that file from the IMDF zip file and tried again but a different error appeared: "No levels were found correlated to directory floors for the building" When the CSV file with building and floor data was uploaded before the configuration step, I didn't add any SMTP address values in that column because they don't exist yet. When the import script finished, a few errors appeared stating that an identity wasn't found. Maybe that's part of the issue? I'm not sure what I'm missing. Anyone else made it through this step yet in the public preview?Solved821Views0likes4Comments