fix(azure): remove duplicated findings in entra_user_with_vm_access_has_mfa

[HugoPBrito]

Context

The check entra_user_with_vm_access_has_mfa was reporting duplicated findings when a user had multiple roles that grant VM access (e.g., Owner + Virtual Machine Contributor) within the same subscription.

Fix: #9913

Description

This PR fixes the duplication by tracking which user+subscription combinations have already been reported. Once a finding is generated for a user in a subscription, subsequent role assignments for the same combination are skipped.

Changes:

• Added a reported_combinations set to track (user.id, subscription_name) pairs
• Skip processing if the combination was already reported
• Break out of the role assignment loop after generating a finding

Steps to review

1. Review the logic change in entra_user_with_vm_access_has_mfa.py
2. Run the existing tests to verify they still pass
3. Optionally test with an Azure environment where users have multiple VM-related roles

Checklist

Community Checklist

• This feature/issue is listed in here or roadmap.prowler.com
• Is it assigned to me, if not, request it via the issue/feature in here or Prowler Community Slack

• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

SDK/CLI

• Are there new checks included in this PR? No

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[codecov]

Codecov Report

❌ Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 85.99%. Comparing base (e97e31c) to head (f4d2fa5).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #9914       +/-   ##
===========================================
+ Coverage   25.64%   85.99%   +60.35%     
===========================================
  Files         836      222      -614     
  Lines       23761     5692    -18069     
===========================================
- Hits         6093     4895     -1198     
+ Misses      17668      797    -16871     

Flag	Coverage Δ
prowler-py3.10-aws	?
prowler-py3.10-azure	85.99% <80.00%> (?)
prowler-py3.10-config	?
prowler-py3.11-aws	?
prowler-py3.11-azure	85.99% <80.00%> (?)
prowler-py3.11-config	?
prowler-py3.12-aws	?
prowler-py3.12-azure	85.99% <80.00%> (?)
prowler-py3.12-config	?
prowler-py3.9-aws	?
prowler-py3.9-azure	85.99% <80.00%> (?)
prowler-py3.9-config	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
prowler	85.99% <80.00%> (+60.35%)	⬆️
api	∅ <ø> (∅)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

🔒 Container Security Scan

Image: prowler:0746e5d
Last scan: 2026-01-29 11:17:03 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	3
Total	3

3 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

• Review the detailed scan results
• Update affected packages to patched versions
• Consider using a different base image if updates are unavailable

---

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy

[puchy22]

LGTM 👍

[prowler-bot]

💚 All backports created successfully

Status	Branch	Result
✅	v5.17

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details