Microsoft-Teams-Send-Proactive-Messages-to-Any-User

[hyaffe839]

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Related Issues

CIAC-14920

Description

Must have

• Tests
• Documentation

[content-bot]

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

• @content-bot start review - Initiate a full AI code review
• @content-bot re-review - Incremental review for new commits

[content-bot]

⚠️ The PR is missing the ready-for-pipeline-running label. Please add the label when the PR is ready in order to proceed.

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
Packs/MicrosoftTeams/Integrations/MicrosoftTeams
MicrosoftTeams.py	1873	525	71%	311, 317, 380, 382, 422–423, 446, 455, 457, 485–486, 488–491, 493–496, 500, 518, 522, 530–531, 748–749, 782, 805, 898–901, 903–904, 919–920, 929–931, 933–935, 937–939, 941, 948–950, 952–954, 956–963, 965–971, 982, 985, 987, 990–992, 995–996, 998–1007, 1010, 1013–1014, 1016, 1018–1020, 1022, 1024–1025, 1031–1032, 1035, 1041–1043, 1045–1046, 1057–1061, 1063–1064, 1068–1069, 1072–1074, 1076–1079, 1082, 1088–1089, 1091–1092, 1094–1095, 1098–1100, 1102–1103, 1115–1116, 1118–1119, 1122, 1124, 1126–1130, 1132, 1134–1135, 1137–1138, 1147–1148, 1186, 1197, 1204–1206, 1209, 1218–1219, 1240–1241, 1276–1278, 1280–1281, 1292, 1305–1308, 1311–1313, 1316–1318, 1322, 1331–1332, 1336–1337, 1362, 1376–1383, 1385–1389, 1391–1393, 1395–1397, 1400–1403, 1405, 1407–1424, 1426, 1428–1429, 1432–1435, 1437, 1439–1440, 1442–1445, 1447–1448, 1450, 1455, 1457–1461, 1463–1465, 1567–1570, 1578–1581, 1583–1585, 1587–1590, 1592, 1594, 1645, 1647, 1774–1775, 1787, 1859, 1932, 1934, 1937–1939, 1941–1949, 1951–1952, 1954, 1957, 1976, 1981, 1983, 2163–2164, 2170, 2183, 2223, 2402–2403, 2487–2492, 2511–2523, 2624, 2645–2646, 2712, 2721, 2751–2754, 2777–2779, 2792, 2812, 2815, 2818, 2826, 2829–2831, 2837, 2861–2864, 2867–2868, 2870–2871, 2874–2875, 2878–2879, 2882–2887, 2890–2891, 2896, 2903, 2911, 2925–2926, 2929, 2978–2980, 2982, 3017–3024, 3026–3032, 3037–3038, 3040–3049, 3053–3056, 3058, 3084–3085, 3098–3100, 3130, 3136–3138, 3145, 3156–3157, 3160, 3164, 3202–3204, 3251–3252, 3255, 3326, 3330, 3342, 3359–3361, 3381, 3428–3429, 3443, 3449–3451, 3471–3473, 3483, 3485–3492, 3494–3496, 3500–3503, 3529, 3534, 3589–3591, 3593–3594, 3596, 3598–3599, 3601–3602, 3604–3606, 3608, 3610–3614, 3616–3619, 3621–3623, 3625, 3627, 3629–3639, 3641–3647, 3726, 3743, 3788–3791, 3794–3795, 3800, 3810–3811, 3822–3823, 3825, 3834, 3860, 3934, 3959, 3963, 3974, 3977, 3994–3995
TOTAL	1873	525	71%

Tests	Skipped	Failures	Errors	Time
146	0 💤	0 ❌	0 🔥	4.645s ⏱️

[content-bot]

Validate summary
The following errors were thrown as a part of this pr: DS108, BA129.
The following errors can be ignored: DS108, BA129.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: DS108, BA129.

Verdict: PR can be force merged from validate perspective? ✅