syndication scrub part 1

Author: mattbriggs

articles/azure-stack/asdk/asdk-redeploy.md

@@ -14,7 +14,7 @@ pms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
 ms.custom: 
-ms.date: 06/07/2018
+ms.date: 08/01/2018
 ms.author: jeffgilb
 ms.reviewer: misainat
 ---
@@ -26,7 +26,7 @@ In this article, you learn how to redeploy the Azure Stack Development Kit (ASDK
 > Upgrading the ASDK to a new version isn't supported. You have to redeploy the ASDK on the development kit host computer each time you want to evaluate a newer version of Azure Stack.
 
 ## Remove Azure registration 
-If you have previously registered your ASDK installation with Azure, you should remove the registration resource before redeploying the ASDK. Re-register the ASDK to enable marketplace syndication when you redeploy the ASDK. If you have not previously registered the ASDK with your Azure subscription, you can skip this section.
+If you have previously registered your ASDK installation with Azure, you should remove the registration resource before redeploying the ASDK. Re-register the ASDK to enable the availability of items in the marketplace when you redeploy the ASDK. If you have not previously registered the ASDK with your Azure subscription, you can skip this section.
 
 To remove the registration resource, use the **Remove-AzsRegistration** cmdlet to unregister Azure Stack. Then, use the **Remove-AzureRMRsourceGroup** cmdlet to delete the Azure Stack resource group from your Azure subscription:
 

articles/azure-stack/azure-stack-compute-add-scalesets.md

@@ -30,8 +30,8 @@ On Azure Stack, virtual machine scale sets don't support auto-scale. You can add
 
 ## Prerequisites
 
-- **Marketplace syndication**  
-    Register Azure Stack with global Azure to enable Marketplace syndication. Follow the instructions in [Register Azure Stack with Azure](azure-stack-registration.md).
+- **The Marketplace**  
+    Register Azure Stack with global Azure to enable the availability of items in the Marketplace. Follow the instructions in [Register Azure Stack with Azure](azure-stack-registration.md).
 - **Operating system image**  
     If you haven’t added an operating system image to the Azure Stack Marketplace, see [Add an Azure Stack marketplace item from Azure](asdk/asdk-marketplace-item.md).
 

articles/azure-stack/azure-stack-connected-deployment.md

@@ -13,7 +13,7 @@ ms.workload: na
 pms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 02/06/2018
+ms.date: 08/01/2018
 ms.author: jeffgilb
 ms.reviewer: wfayed
 
@@ -36,7 +36,7 @@ When you use Azure AD for your identity store requires two Azure AD accounts: a
 1. **Global admin account** (only required for connected deployments). This is an Azure account that is used to create applications and service principals for Azure Stack infrastructure services in Azure Active Directory. This account must have directory administrator permissions to the directory that your Azure Stack system will be deployed under. It will become the "cloud operator" Global Admin for the Azure AD tenant and will be used: 
     - To provision and delegate applications and service principals for all Azure Stack services that need to interact with Azure Active Directory and Graph API. 
     - As the Service Administrator account. This is the owner of the default provider subscription (which you can later change). You can log into the Azure Stack admin portal with this account, and can use it to create offers and plans, set quotas, and perform other administrative functions in Azure Stack.
-2. **Billing account** (required for both connected and disconnected deployments). This Azure account is used to establish the billing relationship between your Azure Stack integrated system and the Azure commerce backend. This is the account that will be billed for Azure Stack fees. This account will also be used for marketplace syndication and other hybrid scenarios. 
+2. **Billing account** (required for both connected and disconnected deployments). This Azure account is used to establish the billing relationship between your Azure Stack integrated system and the Azure commerce backend. This is the account that will be billed for Azure Stack fees. This account will also be used for offering items in the marketplace and other hybrid scenarios. 
 
 ### AD FS identity store
 Choose this option if you want to use your own identity store, such as your corporate Active Directory, for your Service Administrator accounts.  
@@ -60,7 +60,7 @@ If you are going to use a CSP subscription, review the table below to identify w
 ### Capacity based billing
 If you decide to use the capacity billing model, you must purchase an Azure Stack Capacity Plan SKU based on the capacity of your system. You will need to know the number of physical cores in your Azure Stack to purchase the correct quantity. 
 
-Capacity billing requires an Enterprise Agreement (EA) Azure subscription for registration. The reason is that registration sets up syndication, which requires an Azure subscription. The subscription is not used for Azure Stack usage.
+Capacity billing requires an Enterprise Agreement (EA) Azure subscription for registration. The reason is that registration sets up the availability of items in the Marketplace, which requires an Azure subscription. The subscription is not used for Azure Stack usage.
 
 ## Learn more
 - For information about use cases, purchasing, partners, and OEM hardware vendors, see the [Azure Stack](https://azure.microsoft.com/overview/azure-stack/) product page.

articles/azure-stack/azure-stack-disconnected-deployment.md

@@ -13,7 +13,7 @@ ms.workload: na
 pms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 04/26/2018
+ms.date: 08/01/2018
 ms.author: jeffgilb
 ms.reviewer: wfayed
 
@@ -42,7 +42,7 @@ Azure Stack was designed to work best when connected to Azure, so it’s importa
 |VM deployment with Docker Extension to run Docker commands|Impaired – Docker will check the Internet for the latest version and this check will fail.|
 |Documentation links in the Azure Stack Portal|Unavailable – Links such as Give Feedback, Help, Quickstart, etc. that use an Internet URL won’t work.|
 |Alert remediation/mitigation that references an online remediation guide|Unavailable – Any alert remediation links that use an Internet URL won’t work.|
-|Marketplace syndication – The ability to select and add Gallery packages directly from the Azure Marketplace|Impaired – When you deploy Azure Stack in a disconnected mode (without any internet connectivity), you can’t download marketplace items by using the Azure Stack portal. However, you can use the [marketplace syndication tool](https://docs.microsoft.com/azure/azure-stack/azure-stack-download-azure-marketplace-item#download-marketplace-items-in-a-disconnected-or-a-partially-connected-scenario-with-limited-internet-connectivity) to download the marketplace items to a machine that has internet connectivity and then transfer them to your Azure Stack environment.|
+|Marketplace – The ability to select and add Gallery packages directly from the Azure Marketplace|Impaired – When you deploy Azure Stack in a disconnected mode (without any Internet connectivity), you can’t download marketplace items by using the Azure Stack portal. However, you can use the [marketplace syndication tool](https://docs.microsoft.com/azure/azure-stack/azure-stack-download-azure-marketplace-item#download-marketplace-items-in-a-disconnected-or-a-partially-connected-scenario-with-limited-internet-connectivity) to download the marketplace items to a machine that has internet connectivity and then transfer them to your Azure Stack environment.|
 |Using Azure Active Directory federation accounts to manage an Azure Stack deployment|Unavailable – This feature requires connectivity to Azure. AD FS with a local Active Directory instance must be used instead.|
 |App Services|Impaired - WebApps may require Internet access for updated content.|
 |Command Line Interface (CLI)|Impaired – CLI has reduced functionality in terms of authentication and provisioning of Service Principles.|

articles/azure-stack/azure-stack-download-azure-marketplace-item.md

@@ -26,7 +26,7 @@ As a cloud operator, download items from the Azure Marketplace and make them ava
 There are two scenarios for connecting to the Azure Marketplace: 
 
 - **A connected scenario** - that requires your Azure Stack environment to be connected to the internet. You use the Azure Stack portal to locate and download items. 
-- **A disconnected or partially connected scenario** - that requires you to access the internet using the marketplace syndication tool to download marketplace items. Then, you transfer your downloads to your disconnected Azure Stack installation. This scenario uses PowerShell.
+- **A disconnected or partially connected scenario** - that requires you to access the Internet using the marketplace syndication tool to download marketplace items. Then, you transfer your downloads to your disconnected Azure Stack installation. This scenario uses PowerShell.
 
 See [Azure Marketplace items for Azure Stack](azure-stack-marketplace-azure-items.md) for a list of the marketplace items you can download.
 

articles/azure-stack/azure-stack-identity-architecture.md

@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: get-started-article
-ms.date: 2/28/2018
+ms.date: 08/01/2018
 ms.author: brenduns
 ms.reviewer:
 ---
@@ -31,7 +31,7 @@ The identity provider that you choose can limit your options, including support
 |------------------------------|----------|-------|
 |Connected to the internet     |Yes       |Optional|
 |Support for multi-tenancy     |Yes       |No      |
-|Marketplace syndication       |Yes       |Yes. Requires use of the [offline Marketplace Syndication](azure-stack-download-azure-marketplace-item.md#disconnected-or-a-partially-connected-scenario) tool.|
+|Offer items in the Marketplace |Yes       |Yes. Requires use of the [offline Marketplace Syndication](azure-stack-download-azure-marketplace-item.md#disconnected-or-a-partially-connected-scenario) tool.|
 |Support for Active Directory Authentication Library (ADAL) |Yes |Yes|
 |Support for tools such as Azure CLI, Visual Studio, and PowerShell  |Yes |Yes|
 |Create service principals through the Azure portal     |Yes |No|

articles/azure-stack/azure-stack-integrate-endpoints.md

@@ -62,7 +62,7 @@ Azure Stack supports only transparent proxy servers. In a deployment where a tra
 |Purpose|URL|Protocol|Ports|
 |---------|---------|---------|---------|
 |Identity|login.windows.net<br>login.microsoftonline.com<br>graph.windows.net<br>https://secure.aadcdn.microsoftonline-p.com|HTTP<br>HTTPS|80<br>443|
-|Marketplace syndication|https://management.azure.com<br>https://&#42;.blob.core.windows.net<br>https://*.azureedge.net<br>https://&#42;.microsoftazurestack.com|HTTPS|443|
+|Marketplace |https://management.azure.com<br>https://&#42;.blob.core.windows.net<br>https://*.azureedge.net<br>https://&#42;.microsoftazurestack.com|HTTPS|443|
 |Patch & Update|https://&#42;.azureedge.net|HTTPS|443|
 |Registration|https://management.azure.com|HTTPS|443|
 |Usage|https://&#42;.microsoftazurestack.com<br>https://*.trafficmanager.net|HTTPS|443|

articles/azure-stack/azure-stack-integrate-identity.md

@@ -6,7 +6,7 @@ author: jeffgilb
 manager: femila
 ms.service: azure-stack
 ms.topic: article
-ms.date: 07/16/2018
+ms.date: 08/01/2018
 ms.author: jeffgilb
 ms.reviewer: wfayed
 keywords:
@@ -21,7 +21,7 @@ The following table shows the differences between the two identity choices:
 |---------|---------|---------|
 |Billing|Must be Capacity<br> Enterprise Agreement (EA) only|Capacity or Pay-as-you-use<br>EA or Cloud Solution Provider (CSP)|
 |Identity|Must be AD FS|Azure AD or AD FS|
-|Marketplace syndication|Supported<br>BYOL licensing|Supported<br>BYOL licensing|
+|Marketplace |Supported<br>BYOL licensing|Supported<br>BYOL licensing|
 |Registration|Recommended, requires removable media<br> and a separate connected device.|Automated|
 |Patch and update|Required, requires removable media<br> and a separate connected device.|Update package can be downloaded directly<br> from the Internet to Azure Stack.|
 

articles/azure-stack/azure-stack-marketplace-azure-items.md

@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 07/02/2018
+ms.date: 08/01/2018
 ms.author: brenduns
 ms.reviewer: jeffgo
 

articles/azure-stack/azure-stack-network.md

@@ -13,7 +13,7 @@ ms.workload: na
 pms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 07/12/2018
+ms.date: 08/01/2018
 ms.author: jeffgilb
 ms.reviewer: wamota
 ---
@@ -81,7 +81,7 @@ You'll need to make Azure Stack services available to users from outside Azure S
 ### Ports and URLs
 To make Azure Stack services (such as the portals, Azure Resource Manager, DNS, etc.) available to external networks, you must allow inbound traffic to these endpoints for specific URLs, ports, and protocols.
 
-In a deployment where a transparent proxy uplinks to a traditional proxy server, you must allow specific ports and URLs for both [inbound](https://docs.microsoft.com/azure/azure-stack/azure-stack-integrate-endpoints#ports-and-protocols-inbound) and [outbound](https://docs.microsoft.com/azure/azure-stack/azure-stack-integrate-endpoints#ports-and-urls-outbound) communication. These include ports and URLs for identity, marketplace syndication, patch and update, registration, and usage data.
+In a deployment where a transparent proxy uplinks to a traditional proxy server, you must allow specific ports and URLs for both [inbound](https://docs.microsoft.com/azure/azure-stack/azure-stack-integrate-endpoints#ports-and-protocols-inbound) and [outbound](https://docs.microsoft.com/azure/azure-stack/azure-stack-integrate-endpoints#ports-and-urls-outbound) communication. These include ports and URLs for identity, the marketplace, patch and update, registration, and usage data.
 
 ## Next steps
 [Border connectivity](azure-stack-border-connectivity.md)