Fix IPinfo connectors: runtime pinning, dependency updates, and multi…

[Prasanna92Sekar]

PR Summary

• This PR focuses on improving deployment reliability and installation stability for the IPinfo data connector.

What’s included in this PR:
Change(s):

• Added missing native dependency (cffi) to ensure reliable Function App startup and publishing.
• Pinned Azure Functions runtime to v4 and verified Python 3.11 is correctly picked up during deployment.
• Standardized DCR workspace validation and creation logic across IPinfo Azure Functions to support multi-workspace deployments.
• Applied the same DCR handling logic consistently across IPinfo connectors.
• Verified end-to-end log ingestion; data ingestion has been tested and confirmed working.

Reason for Change(s):

• See guidance below

Version Updated:

• 3.0.2

Testing Completed:
-- tested log ingestion to worksapce table.

Pending / Follow-ups:
-- aka.ms short link is required for final Marketplace/Solution readiness.

What’s intentionally out of scope (next PR):

• Further enhancements to other data connector multi-workspace behavior will be handled in a follow-up PR, after validating stability in this release.

Please confirm when it’s okay to add the short link, and I’ll update it accordingly.

Guidance <- remove section before submitting

---

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:

Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR. Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process. Providing associated Issues that this resolves also easily connects the reason.

Change(s):

• Updated syntax for XYZ.yaml

Reason for Change(s):

• New schema used for XYZ.yaml
• Resolves ISSUE Add Logstash required version to Readme file #1234

Version updated:

• Yes
• Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly. If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

• Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

• Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

• Guidance for Detection checks
• General contribution guidance
• PR validation troubleshooting

---