Skip to content

Commit 1e6da4c

Browse files
committed
Merge remote-tracking branch 'upstream/main' into AB#6973-Blocking-users-from-running-Hyper-V-and-VMware-virtual-machines
2 parents bfb788b + 99d3e6a commit 1e6da4c

27 files changed

Lines changed: 702 additions & 551 deletions

.openpublishing.redirection.json

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13801,6 +13801,41 @@
1380113801
"redirect_url": "/previous-versions/troubleshoot/sql/tools/error-you-run-sqlmaint-utility",
1380213802
"redirect_document_id": false
1380313803
},
13804+
{
13805+
"source_path": "support/azure/azure-monitor/activity-logs/config-export/centralized-configuration-of-activity-logs-to-event-hub.md",
13806+
"redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
13807+
}
13808+
,
13809+
{
13810+
"source_path": "support/azure/azure-monitor/activity-logs/config-export/exporting-directory-level-activity-logs-to-event-hub.md",
13811+
"redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
13812+
}
13813+
,
13814+
{
13815+
"source_path": "support/azure/azure-monitor/activity-logs/config-export/pushing-subscription-activity-logs-to-sentinel.md",
13816+
"redirect_url": "/troubleshoot/azure/azure-monitor/activity-logs/config-export/push-subscription-activity-logs-to-sentinel"
13817+
}
13818+
,
13819+
{
13820+
"source_path": "support/azure/azure-monitor/activity-logs/config-export/resolving-log-limit-issues-in-azure-function-apps.md",
13821+
"redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
13822+
}
13823+
,
13824+
{
13825+
"source_path": "support/azure/azure-monitor/activity-logs/config-export/understanding-and-managing-diagnostic-settings-retention.md",
13826+
"redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
13827+
}
13828+
,
13829+
{
13830+
"source_path": "support/azure/azure-monitor/activity-logs/config-export/understanding-and-transitioning-from-legacy-to-diagnostic-settings.md",
13831+
"redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
13832+
}
13833+
,
13834+
{
13835+
"source_path": "support/azure/azure-monitor/activity-logs/config-export/diagnostic-settings-transition-from-legacy-solutions.md",
13836+
"redirect_url": "/troubleshoot/azure/azure-monitor/welcome-azure-monitor"
13837+
}
13838+
,
1380413839
{
1380513840
"source_path": "support/sql/database-engine/install/windows/error-install-sql-server-2008-r2.md",
1380613841
"redirect_url": "/troubleshoot/sql/database-engine/install/windows/error-install-sql-server"

Microsoft365/purview/data-loss-prevention/collect-compliance-diagnostics.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,9 @@ Getting Autolabeling rules in your organization.
110110
Getting IB labels in your organization.
111111
Getting IB policies in your organization.
112112
Getting IB Application Status for your organization.
113+
Getting IB Configuration from ExO.
114+
Getting Hold Policy, Rules for your Organization.
115+
Getting DLM Policies and Rules for your Organization.
113116
Starting UX......
114117
```
115118

@@ -135,6 +138,12 @@ Follow these steps:
135138
- **eDiscovery** \> **Hold**
136139
- **eDiscovery** \> **Search**
137140
- **eDiscovery** \> **Export**
141+
- **Data Lifecycle Management** \> **Archiving**
142+
- **Data Lifecycle Management** \> **Exchange Retention**
143+
- **Data Lifecycle Management** \> **SharePoint Retention**
144+
- **Data Lifecycle Management** \> **Teams Retention**
145+
- **Data Lifecycle Management** \> **Disposition**
146+
- **Data Lifecycle Management** \> **Journaling**
138147

139148
For example, to collect support data for an issue in which a sensitive information type (SIT) is incorrectly detected in a document, select the **Data Classification** \> **Classification** template.
140149

@@ -146,7 +155,7 @@ Follow these steps:
146155

147156
4. In the folder dialog box that opens, select a parent folder for the diagnostic data.
148157

149-
Wait for the tool to finish processing the diagnostic data and write the processed data to an .json file. The tool generates a .zip file that packages the .json file together with any diagnostic files from the template. The tool then saves the .zip file to the parent folder that you selected, and then opens a completion dialog box.
158+
Wait for the tool to finish processing the diagnostic data and write the processed data to a .json file and a .xml file. The tool generates a .zip file that packages the .json file and the .xml file together with any diagnostic files from the template. The tool then saves the .zip file to the parent folder that you selected, and then opens a completion dialog box.
150159

151160
As an example of data processing, if you select the **Data Classification** \> **Classification** template, the tool fetches the applicable rule packs and keyword dictionaries, and then tests data classification on the sample file that you specify in the template.
152161

-10.6 KB
Loading

Teams/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -222,6 +222,8 @@ items:
222222
href: ./phone-system/direct-routing/microsoft-sip-response-codes-503.md
223223
- name: SIP response code 504
224224
href: ./phone-system/direct-routing/microsoft-sip-response-codes-504.md
225+
- name: Resolve 10DLC campaign rejection errors
226+
href: ./phone-system/sms-calling-errors.md
225227
- name: Voicemail messages are not delivered
226228
href: ./phone-system/voicemails-not-delivered.md
227229
- name: Provisioning
Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
---
2+
title: Resolve 10DLC campaign rejection errors
3+
description: Provides a list of potential 10DLC campaign rejection errors, and guidance to resolve them.
4+
ms.date: 08/18/2025
5+
manager: dcscontentpm
6+
audience: Admin
7+
ms.topic: troubleshooting
8+
appliesto:
9+
- Microsoft Teams
10+
ms.custom:
11+
- sap:Teams Calling (PSTN)
12+
- CI 7095
13+
ms.reviewer: julienp, revaldiv
14+
---
15+
# Resolve 10DLC campaign rejection errors
16+
17+
When you enable the [Short Message Service (SMS)](/microsoftteams/sms-overview) feature in Microsoft Teams, you might need to troubleshoot and resubmit [campaigns](/microsoftteams/sms-setup-campaign) that were rejected during the 10-digit-long code (10DLC) review process. After a campaign is submitted, Microsoft and 10DLC operators evaluate it for compliance with Mobile Network Operator (MNO) and industry standards. If the campaign doesn't meet these requirements, it's rejected and generates one or more error codes.
18+
19+
The following sections provide a comprehensive list of potential rejection errors, together with clear descriptions and actionable recommendations to help you resolve issues and successfully resubmit your campaign. The sections are organized by the categories of information that you submit to register a campaign.
20+
21+
## Call to Action
22+
23+
| Error | Description | Recommended action |
24+
|-------|-------------|--------------------|
25+
| CallToActionContainsDisallowedContent | The Call to Action contains disallowed content. | Remove any prohibited content from the Call to Action. |
26+
| CallToActionDoesNotContainRobustAgeGate | The Call to Action doesn't contain a robust age gate for age-restricted content. | Add a clear age verification step for age-restricted campaigns. |
27+
| CallToActionIsMissingOrInaccessible | The Call to Action is missing or inaccessible. | Make sure that the Call to Action is present and accessible to users. |
28+
| CallToActionMissingBrandName | The Call to Action doesn't contain the registered (DBA) brand name. | Add the brand name in the Call to Action. |
29+
| CallToActionMissingDataRatesDisclosure | The Call to Action doesn't include the "message and data rates may apply" disclosure. | Add the required disclosure to inform users about potential charges. |
30+
| CallToActionMissingExplicitConsent | The Call to Action doesn't express explicit or written consent. | Add language that clearly obtains user consent. |
31+
| CallToActionMissingExpressWrittenConsent | The Call to Action doesn't obtain express written consent for promotional message content. | Add a checkbox or statement for express written consent. |
32+
| CallToActionMissingHelpInstructions | The Call to Action doesn't include HELP instructions. | Add HELP instructions for user support. |
33+
| CallToActionMissingMessageFrequencyDisclosure | The Call to Action doesn't include the frequency at which messages are sent. | Add a statement about message frequency. |
34+
| CallToActionMissingPrivacyPolicyLink | The Call to Action or the opt-in form doesn't include a link to the privacy policy. | Add a link to the privacy policy or a statement about data sharing. |
35+
| CallToActionMissingStopInstructions | The Call to Action doesn't contain STOP instructions. | Add STOP instructions to enable users to opt out. |
36+
| CallToActionMissingTermsAndConditions | The Call to Action doesn't contain full terms and conditions or a link to them. | Add the full terms or a link to them. |
37+
| CallToActionMissingVerbalScript | The Call to Action doesn't include a verbal script or required disclosures. | Add a verbal script that has the required disclosures. |
38+
| CallToActionOptInIssues | The opt-in URL is inaccessible or returns a certificate error. | Make sure that the opt-in URL is valid and secure. |
39+
| CallToActionMissingMessageType | The Call to Action doesn't mention the kinds of messages that a customer can expect. | Specify the kinds of messages that users might receive. |
40+
| CallToActionInvalidOrIncomplete | The Call to Action is noncompliant or incomplete. | Make sure that all required elements are present: brand name, HELP, STOP, frequency, fees, privacy policy. |
41+
42+
## Terms and conditions
43+
44+
| Error | Description | Recommended action |
45+
|-------|-------------|--------------------|
46+
| TermsAndConditionsMissing | The terms and conditions document URL is missing or inaccessible. | Provide a valid and accessible URL for terms and conditions. |
47+
| TermsAndConditionsMissingBrandName | The terms and conditions document doesn't contain the registered (DBA) brand name. | Add the brand name in the terms and conditions document. |
48+
| TermsAndConditionsMissingCustomerSupportInformation | The terms and conditions document doesn't contain customer support contact information. | Add customer support contact details. |
49+
| TermsAndConditionsMissingMessageFrequency | The terms and conditions document doesn't contain a message frequency disclosure. | Add message frequency information. |
50+
| TermsAndConditionsMissingOptOutInstructions | The terms and conditions document doesn't contain information about how to opt out. | Add STOP instructions. |
51+
| TermsAndConditionsMissingPrivacyPolicyLink | The terms and conditions document doesn't contain a link to the privacy policy. | Add a link to the privacy policy. |
52+
| TermsAndConditionsMissingProgramDescription | The terms and conditions document doesn't contain a description of the message program. | Add a description of the message program's purpose. |
53+
| TermsAndConditionsMissingSweepstakesTerms | The terms and conditions document doesn't contain sweepstakes terms, as applicable. | Add sweepstakes terms if the campaign involves sweepstakes. |
54+
55+
## Privacy policy
56+
57+
| Error | Description | Recommended action |
58+
|-------|-------------|--------------------|
59+
| PrivacyPolicyDataSharingIssue | The privacy policy indicates that mobile opt-in data might be shared with third parties. | Update the policy to explicitly state that data isn't shared with third parties. |
60+
| PrivacyPolicyMissingOrInvalid | The privacy policy URL is invalid or is missing required elements. | Provide a valid URL and make sure that all required elements are included. |
61+
62+
## Opt-in message
63+
64+
| Error | Description | Recommended action |
65+
|-------|-------------|--------------------|
66+
| OptInMessageMissingMandatoryMessageTerminology | The opt-in message is missing key elements. | Add brand name, HELP, STOP, frequency, and fee disclosures. |
67+
| OptInMessageMissingBrandName | The opt-in message doesn't contain the brand name. | Add the registered (DBA) brand name. |
68+
| OptInMessageMissingDataRatesDisclosure | The opt-in message doesn't contain the "message and data rates may apply" disclosure. | Add the required disclosure. |
69+
| OptInMessageMissingHelpInstructions | The opt-in message doesn't include HELP instructions. | Add HELP instructions. |
70+
| OptInMessageMissingMessageFrequency | The opt-in message doesn't contain a message frequency disclosure. | Add message frequency information. |
71+
| OptInMessageMissingOptOutInstructions | The opt-in message doesn't include opt-out instructions. | Add STOP instructions. |
72+
| MandatoryMessageTerminologyMissing | Required message terminology is missing. | Add all mandatory terms: brand name, HELP, STOP, frequency, fees. |
73+
74+
## Opt-out message
75+
76+
| Error | Description | Recommended action |
77+
|-------|-------------|--------------------|
78+
| OptOutMessageMissingBrandName | The opt-out message doesn't contain the brand name. | Add the registered (DBA) brand name. |
79+
| OptOutMessageMissingBrandNameOrConfirmation | The opt-out message doesn't contain the brand name or confirmation. | Add the brand name and confirm that no further messages will be sent. |
80+
| OptOutMessageMissingConfirmation | The opt-out message doesn't confirm that no further messages will be sent. | Add confirmation that messaging will stop. |
81+
| MandatoryMessageTerminologyMissing | Required message terminology is missing. | Add brand name, STOP, confirmation, and fee disclosures. |
82+
83+
## Help message
84+
85+
| Error | Description | Recommended action |
86+
|-------|-------------|--------------------|
87+
| HelpMessageNotMatchingBrandSupportContactEmail | The support contact email address doesn't match the registered brand support email. | Make sure that the support email address matches the brand's registered contact information. |
88+
| HelpMessageMissingBrandName | The HELP message doesn't contain the brand name. | Add the registered (DBA) brand name. |
89+
| HelpMessageMissingSupportContact | The HELP message doesn't include customer support contact information. | Add customer support contact details. |
90+
| MandatoryMessageTerminologyMissing | Required message terminology is missing. | Add brand name, HELP, STOP, frequency, fees. |
91+
92+
## Sample messages
93+
94+
| Error | Description | Recommended action |
95+
|-------|-------------|--------------------|
96+
| SampleMessageContainsDisallowedContent | The sample messages contain disallowed content. | Remove prohibited content such as SHAFT, gambling, and illegal services. |
97+
| SampleMessageContainsPublicURLShortener | The sample messages contain public URL shorteners. | Replace public shorteners with branded or full URLs. |
98+
| SampleMessageMissing | The sample messages are missing or insufficient. | Provide at least two complete sample messages. |
99+
| SampleMessageMissingBrandName | The sample messages don't contain the brand name. | Add the registered (DBA) brand name to all samples. |
100+
| SampleMessageMissingOptOutInstructions | The sample messages don't contain opt-out instructions. | Add STOP instructions to each sample message. |
101+
| SampleMessageUseCaseMismatch | The sample messages don't match the declared use cases. | Make sure that sample messages reflect the declared use case accurately. |
102+
103+
## Campaign (use case, description, and attributes)
104+
105+
| Error | Description | Recommended action |
106+
|-------|-------------|--------------------|
107+
| CampaignAttributesMissingOrInvalid | The campaign attributes are missing or invalid or not configured correctly. | Review the campaign attributes and make sure that all required fields are filled correctly. |
108+
| CampaignAttributesNotMatchingCampaignDescription | The campaign attributes phone number or link is set to False, but the campaign description indicates a phone number or link. | Update the campaign attributes to match the description, especially regarding phone numbers and links. |
109+
| CampaignContainsDisallowedContent | The campaign description includes disallowed content such as gambling, high-risk financial services, illegal substances, or SHAFT content. | Remove any SHAFT content or other prohibited categories. Review CTA guidelines for compliance. |
110+
| CampaignDescriptionNotMatchingBrandName | The submitted legal company name doesn't match the provided tax ID. | Make sure that the brand name matches the legal entity and tax ID records. |
111+
| CampaignDescriptionNotMatchingUseCase | The campaign description doesn't sufficiently describe the service or doesn't match the declared use cases. | Update the campaign description to clearly describe the service and align the description with the declared use cases. |
112+
| CampaignDescriptionNotUnique | The campaign description isn't unique or is a duplicate. | Modify the campaign description to be unique and specific to the brand's use case. |
113+
114+
## Brand
115+
116+
| Error | Description | Recommended action |
117+
|-------|-------------|--------------------|
118+
| BrandAddressInvalid | The physical address of the brand is invalid or unverifiable. | Verify brand address. Contact support to update the address or appeal the decision.|
119+
| BrandAssociatedWithDisallowedContent | The brand is associated with disallowed content. | Remove any association with SHAFT or other prohibited content. |
120+
| BrandAssociatedWithSpamScam | The brand or its address is associated with known spam or scam complaints. | Make sure that the brand isn't flagged for spam or scam activity. Contact support to appeal the decision, as applicable. |
121+
| BrandEmailIssues | The brand email address is missing or invalid or hosted on a free domain. | Verify the brand contact email address. Contact support to update the brand email address or to appeal the decision. |
122+
| BrandEntityTypeSoleProprietorsNotSupported | Sole proprietor campaigns must be associated with a brand that doesn't have a registered tax ID. | Provide a valid EIN or register the brand as a business entity. |
123+
| BrandIdentifiedAsResellerOrIvr | The brand is a reseller or ISV and not the actual content provider. | Make sure that the brand is the actual content provider, not a reseller or ISV. |
124+
| BrandNotAllowed | The brand isn't allowed by 10DLC operators and can't run a campaign. | Contact support to verify brand eligibility or appeal the restriction. |
125+
| BrandPhoneNumberMissingOrInvalid | The brand phone number is missing or invalid. | Verify brand contact phone number. Contact support to update the brand phone number or to appeal the decision. |
126+
| BrandVettingScoreRequirementNotMet | The brand doesn't meet the minimum vetting score requirements. | Contact support to improve the vetting score or to appeal the decision. |
127+
| BrandWebsiteIssues | The brand website URL is missing, doesn't match the brand name, is inaccessible, or doesn't reflect the campaign's declared use case. | Verify that the brand website is valid and has an accessible website URL. Make sure that the site is live and reflects the brand identity. Contact support to update the brand website or to appeal the decision.|
128+
| BrandCampaignMismatch | The brand's name and website don't match, or the sample messages are incomplete or are missing the brand name. | Make sure that the brand name and website are consistent and that sample messages include the brand name. |

0 commit comments

Comments
 (0)