Merge pull request #9192 from MicrosoftDocs/main

Auto push to live 2025-06-25 10:01:54

Author: Deland-Han

.acrolinx-config.edn

@@ -1,2 +1,2 @@
 {:allowed-branchname-matches ["main"]
- :allowed-filename-matches ["support/"]}
+ :allowed-filename-matches ["Exchange/" "Microsoft365/" "Office/" "Outlook/" "SharePoint/" "SkypeforBusiness/" "Teams/" "Viva/" "support/"]}

.openpublishing.publish.config.json

@@ -24,55 +24,65 @@
       "build_output_subfolder": "SupportArticles-Exchange",
       "locale": "en-us",
       "monikers": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
-        "Conceptual": "Content"
+        "Conceptual": "Content",
+        "ManagedReference": "Content",
+        "RestApi": "Content"
       },
-      "build_entry_point": "docs"
+      "build_entry_point": "docs",
+      "template_folder": "_themes"
     },
     {
       "docset_name": "SupportArticles-M365",
       "build_source_folder": "Microsoft365",
       "build_output_subfolder": "SupportArticles-M365",
       "locale": "en-us",
       "monikers": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
-        "Conceptual": "Content"
+        "Conceptual": "Content",
+        "ManagedReference": "Content",
+        "RestApi": "Content"
       },
-      "build_entry_point": "docs"
+      "build_entry_point": "docs",
+      "template_folder": "_themes"
     },
     {
       "docset_name": "SupportArticles-Office",
       "build_source_folder": "Office",
       "build_output_subfolder": "SupportArticles-Office",
       "locale": "en-us",
       "monikers": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
-        "Conceptual": "Content"
+        "Conceptual": "Content",
+        "ManagedReference": "Content",
+        "RestApi": "Content"
       },
-      "build_entry_point": "docs"
+      "build_entry_point": "docs",
+      "template_folder": "_themes"
     },
     {
       "docset_name": "SupportArticles-Outlook",
       "build_source_folder": "Outlook",
       "build_output_subfolder": "SupportArticles-Outlook",
       "locale": "en-us",
       "monikers": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
         "Conceptual": "Content"
       },
-      "build_entry_point": "docs"
+      "build_entry_point": "docs",
+      "template_folder": "_themes"
     },
     {
       "docset_name": "SupportArticles-SharePoint",
       "build_source_folder": "SharePoint",
       "build_output_subfolder": "SupportArticles-SharePoint",
       "locale": "en-us",
       "monikers": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
         "Conceptual": "Content"
       },
@@ -84,31 +94,37 @@
       "build_output_subfolder": "SupportArticles-SkypeForBusiness",
       "locale": "en-us",
       "monikers": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
-        "Conceptual": "Content"
+        "Conceptual": "Content",
+        "ManagedReference": "Content",
+        "RestApi": "Content"
       },
-      "build_entry_point": "docs"
+      "build_entry_point": "docs",
+      "template_folder": "_themes"
     },
     {
       "docset_name": "SupportArticles-Teams",
       "build_source_folder": "Teams",
       "build_output_subfolder": "SupportArticles-Teams",
       "locale": "en-us",
       "monikers": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
-        "Conceptual": "Content"
+        "Conceptual": "Content",
+        "ManagedReference": "Content",
+        "RestApi": "Content"
       },
-      "build_entry_point": "docs"
+      "build_entry_point": "docs",
+      "template_folder": "_themes"
     },
     {
       "docset_name": "SupportArticles-Viva",
       "build_source_folder": "Viva",
       "build_output_subfolder": "SupportArticles-Viva",
       "locale": "en-us",
       "monikers": [],
-      "open_to_public_contributors": false,
+      "open_to_public_contributors": true,
       "type_mapping": {
         "Conceptual": "Content"
       },

Exchange/ExchangeHybrid/administration/cannot-add-and-verify-domain.md

@@ -0,0 +1,65 @@
+---
+title: Can't add and verify a domain in hybrid
+description: Fixes an issue that prevents you from verifying a domain in Microsoft 365 when you have an Exchange hybrid deployment.
+author: cloud-writer
+ms.author: meerak
+manager: dcscontentpm
+audience: ITPro
+ms.topic: troubleshooting
+ms.custom: 
+  - sap:Hybrid
+  - Exchange Hybrid
+  - CSSTroubleshoot
+ms.reviewer: rayfong, v-six
+appliesto: 
+  - Exchange Online
+  - Exchange Server 2013 Enterprise
+  - Exchange Server 2013 Standard Edition
+  - Exchange Server 2010 Enterprise
+  - Exchange Server 2010 Standard
+search.appverid: MET150
+ms.date: 01/24/2024
+---
+# An error occurred while working on your domain when you verify your domain in a hybrid deployment
+
+_Original KB number:_   3089230
+
+> [!NOTE]
+> The Hybrid Configuration wizard that's included in the Exchange Management Console in Microsoft Exchange Server 2010 is no longer supported. Therefore, you should no longer use the old Hybrid Configuration wizard. Instead, use the [Microsoft 365 Hybrid Configuration wizard](https://aka.ms/hybridwizard). For more information, see [Microsoft 365 Hybrid Configuration wizard for Exchange 2010](https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-hybrid-configuration-wizard-for-exchange-2010/ba-p/604541).
+
+## Problem
+
+You have a hybrid deployment of on-premises Exchange Server and Exchange Online in Microsoft 365. When you try to add and verify a domain in the Microsoft 365 admin center, you receive the following error message after you add the TXT record or MX record:
+
+> An error occurred while working on your domain. Please go back to the Domains page to restart the process.
+
+When you go to the **Domains** page, you're redirected to the **Domain Setup** page. However, a new TXT or MX record is generated. After you update the TXT or MX record, you receive the same error message again. You cannot verify the domain.
+
+## Cause
+
+The domain name that you're trying to add to Microsoft 365 is already being used in the on-premises Exchange federation trust as the primary federation organization identifier (`ApplicationUri`).
+
+> [!NOTE]
+> To confirm that this is the cause of the issue, open the Exchange Management Shell, and then run the `Get-FederationTrust` cmdlet to locate the `ApplicationUri` attribute. Confirm that the `ApplicationUri` attribute is set to the domain name that you're trying to verify in Microsoft 365.
+
+## Solution
+
+To resolve this issue, follow these steps:
+
+1. Remove the on-premises federation trust. For more info, see the following:
+   - In Exchange Server 2013: [Remove a federation trust](/exchange/remove-a-federation-trust-exchange-2013-help).
+   - In Exchange Server 2010: [Remove a Federation Trust](/previous-versions/office/exchange-server-2010/dd297972(v=exchg.141)).
+
+2. Add and verify the domain in Microsoft 365. For more info, see [Add a domain to Microsoft 365](/microsoft-365/admin/setup/add-domain).
+
+3. Re-create the on-premises federation trust. For more info, see the following:
+   - In Exchange Server 2013: [Configure a federation trust](/exchange/configure-a-federation-trust-exchange-2013-help).
+   - In Exchange Server 2010: [Create a Federation Trust](/previous-versions/office/exchange-server-2010/dd335198(v=exchg.141)).
+
+4. Re-create the organization relationship at the organization with whom you have set up the organization relationship. For more info, see the following:
+   - In Exchange Server 2013: [Create an organization relationship](/exchange/create-an-organization-relationship-exchange-2013-help).
+   - In Exchange Server 2010: [Create an Organization Relationship](/previous-versions/office/exchange-server-2010/dd351260(v=exchg.141)).
+
+## More information
+
+Still need help? Go to [Microsoft Community](https://answers.microsoft.com/) or the [Exchange TechNet Forums](/answers/topics/office-exchange-server-itpro.html).

Exchange/ExchangeHybrid/administration/cannot-set-up-hybrid-deployment.md

@@ -0,0 +1,50 @@
+---
+title: Can't set up a hybrid deployment when you run Set-FederatedOrganizationIdentifier cmdlet
+description: Describes an issue in which you receive an error when you run Set-FederatedOrganizationIdentifier cmdlet to set up a hybrid deployment.
+manager: dcscontentpm
+audience: ITPro
+ms.topic: troubleshooting
+ms.custom: 
+  - sap:Hybrid
+  - CSSTroubleshoot
+appliesto: 
+- Exchange Online 
+- Exchange Server 2013 Enterprise 
+- Exchange Server 2013 Standard Edition 
+- Exchange Server 2010 Enterprise 
+- Exchange Server 2010 Standard
+search.appverid: MET150
+ms.reviewer: scotro, v-six
+author: cloud-writer
+ms.author: meerak
+ms.date: 01/24/2024
+---
+
+# "InternalError InternalError: Internal error" when you run Set-FederatedOrganizationIdentifier to set up a hybrid deployment
+
+> [!NOTE]
+> The Hybrid Configuration wizard that's included in the Exchange Management Console in Microsoft Exchange Server 2010 is no longer supported. Therefore, you should no longer use the old Hybrid Configuration wizard. Instead, use the Microsoft 365 Hybrid Configuration wizard that's available at [Microsoft.Online.CSE.Hybrid.Client](https://aka.ms/hybridwizard). For more information, see [Microsoft 365 Hybrid Configuration wizard for Exchange 2010](https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-hybrid-configuration-wizard-for-exchange-2010/ba-p/604541).
+
+## Symptoms
+
+You want to set up a hybrid deployment between your on-premises Exchange Server organization and an external federated organization. However, when you run the Set-FederatedOrganizationIdentifier cmdlet, the operation isn't successful, and you receive an "InternalError InternalError: Internal error" error message. The full text of the message resembles the following:
+
+> ERROR: Updating hybrid configuration failed with error 'Subtask Configure execution failed: Creating Organization Relationships.  
+>
+> Execution of the Set-FederatedOrganizationIdentifier cmdlet had thrown an exception. This may indicate invalid parameters in your Hybrid Configuration settings.
+An error occurred while attempting to provision Exchange to the Partner STS. Detailed Information "An unexpected result was received from Windows Live. Detailed information: "InternalError InternalError: Internal error.".".
+at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, Dictionary`2 parameters, Boolean ignoreNotFoundErrors)'.
+
+## Cause
+
+This problem occurs if the domain name for your organization was previously in use and you try to reconfigure the domain. A domain name may be blocked in Windows Live for the Microsoft Entra authentication system if the domain name was previously used.
+
+## Resolution
+
+To resolve this problem, contact [Microsoft Support](https://support.microsoft.com/), and reference this Knowledge Base article.
+
+## More information
+
+See [Set-FederatedOrganizationIdentifier](/powershell/module/exchange/set-federatedorganizationidentifier) for more information.
+
+Still need help? Go to [Microsoft Community](https://answers.microsoft.com/) or the [Exchange TechNet Forums](https://social.technet.microsoft.com/forums/exchange/home?category=exchange2010%2cexchangeserver).

Exchange/ExchangeHybrid/administration/delay-when-outlook-retrieves-autodiscover-information.md

@@ -0,0 +1,74 @@
+---
+title: Delay when Outlook retrieves Autodiscover info
+description: Describes an issue that triggers a delay or other unexpected behavior when Outlook tries to retrieve Autodiscover information for an Exchange Online mailbox in a hybrid deployment.
+author: cloud-writer
+ms.author: meerak
+manager: dcscontentpm
+audience: ITPro
+ms.topic: troubleshooting
+ms.custom: 
+  - sap:Hybrid
+  - Exchange Hybrid
+  - CSSTroubleshoot
+ms.reviewer: andypunt, jmartin, v-six
+appliesto: 
+  - Exchange Online
+  - Exchange Server 2016 Enterprise Edition
+  - Exchange Server 2016 Standard Edition
+  - Exchange Server 2013 Enterprise
+  - Exchange Server 2013 Standard Edition
+  - Exchange Server 2010 Enterprise
+  - Exchange Server 2010 Standard
+search.appverid: MET150
+ms.date: 01/24/2024
+---
+# Delay when Outlook retrieves Autodiscover information for an Exchange Online mailbox in a hybrid environment
+
+_Original KB number:_   3137323
+
+## Symptoms
+
+When Outlook tries to retrieve Autodiscover information for an Exchange Online mailbox in an Exchange hybrid environment, you may experience a delay or unexpected results.
+
+## Cause
+
+The client is locating one or more service connection point (SCP) objects for the Autodiscover service in the local Active Directory forest.
+
+## Resolution 1 - Disable SCP lookup
+
+> [!IMPORTANT]
+> Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, [back up the registry for restoration](https://support.microsoft.com/help/322756) in case problems occur.
+
+1. Open Registry Editor.
+2. Locate and then select the following registry subkey:
+
+   `HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\AutoDiscover`
+
+    > [!NOTE]
+    > The **x.0** placeholder corresponds to the version of Outlook (16.0 = Outlook 2016, 15.0 = Outlook 2013).
+
+3. On the **Edit** menu, point to **New**, and then select **DWORD Value**.
+4. Type *ExcludeScpLookup*, and then press Enter.
+5. Right-click the **ExcludeScpLookup** value that you created, select **Modify**, type *1* in the **Value data** box, and then select **OK**.
+
+To control Outlook Autodiscover by using Group Policy, see [How to control Outlook AutoDiscover by using Group Policy](/outlook/troubleshoot/profiles-and-accounts/how-to-control-autodiscover-via-group-policy).
+
+## Resolution 2 - Remove the Exchange SCP objects
+
+> [!WARNING]
+> This procedure requires Active Directory Service Interfaces Editor (ADSI Edit). Using ADSI Edit incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems that result from the incorrect use of ADSI Edit can be resolved. Use ADSI Edit at your own risk.
+
+1. Open ADSI Edit.
+2. Right-click **ADSI Edit**, select **Connect to**, select **Configuration** in the **Select a well known Naming Context** box, and then select **OK**.
+3. Locate the following container:
+
+   CN=Servers,CN=Exchange Administrative Group,CN=Administrative Groups,CN=\<Exchange Org>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=\<Domain>,DC=\<com>
+
+4. Expand the server, expand **Protocols**, and then expand **Autodiscover**.
+5. Right-click the SCP object (the object is equal to CN=\<ServerName>), and then select **Delete**.
+6. Select **Yes** to confirm the deletion.
+7. Repeat steps 4-6 for each additional server that's listed in the container in step 3.
+
+## More information
+
+Still need help? Go to [Microsoft Community](https://answers.microsoft.com/) or the [Microsoft Q&A](/answers/products/?WT.mc_id=msdnredirect-web-msdn).