Merge pull request #174821 from kenwith/remove-references-feedback-email

Remove references to feedback email as it is being deprecated.

Author: v-albemi

articles/active-directory/app-proxy/application-proxy-configure-hard-coded-link-translation.md

@@ -138,10 +138,6 @@ Getting started with link translation is as easy as clicking a button:
 
 Now, when your users access this application, the proxy will automatically scan for internal URLs that have been published through Application Proxy on your tenant.
 
-## Send feedback
-
-We want your help to make this feature work for all your apps. We search over 30 tags in HTML and CSS. If you have an example of generated links that aren't being translated, send a code snippet to [Application Proxy Feedback](mailto:[email protected]). 
-
 ## Next steps
 [Use custom domains with Azure AD Application Proxy](application-proxy-configure-custom-domain.md) to have the same internal and external URL
 

articles/active-directory/app-proxy/application-proxy-faq.yml

@@ -179,7 +179,7 @@ sections:
       - question: |
          Can I configure Application Proxy to add the HSTS header?
         answer: |
-              Application Proxy does not automatically add the HTTP Strict-Transport-Security header to HTTPS responses, but it will maintain the header if it is in the original response sent by the published application. Proving a setting to enable this functionality is on the roadmap. If you are interested in a preview that enables adding this to responses, reach out to [email protected] for details.
+              Application Proxy does not automatically add the HTTP Strict-Transport-Security header to HTTPS responses, but it will maintain the header if it is in the original response sent by the published application. Proving a setting to enable this functionality is on the roadmap.
 
       - question: |
          Integrated Windows authentication
@@ -286,7 +286,7 @@ sections:
       - question: |
          Does WebSocket support work for applications other than QlikSense and Remote Desktop Web Client (HTML5)?
         answer: |
-              Currently, WebSocket protocol support is still in public preview and it may not work for other applications. Some customers have had mixed success using WebSocket protocol with other applications. If you test such scenarios, we would love to hear your results. Please send us your feedback at [email protected].
+              Currently, WebSocket protocol support is still in public preview and it may not work for other applications. Some customers have had mixed success using WebSocket protocol with other applications.
           
               Features (Eventlogs, PowerShell and Remote Desktop Services) in Windows Admin Center (WAC) do not work through Azure AD Application Proxy presently.
           

articles/active-directory/app-proxy/application-proxy-page-load-speed-problem.md

@@ -22,10 +22,5 @@ Although your applications are working, they can experience a long latency. Ther
 
 Besides network topology, there are currently no further recommendations for performance tuning. As the Application Proxy service expands it might come to a data center that is physically closer. The closer proximity might help with latency. For a list of Azure data centers, see the [latency test page](http://www.azurespeed.com/Azure/Latency). 
 
-## Feedback on Application Proxy data center locations 
-There may be Azure data centers that don’t yet include Application Proxy, but would lead to a great latency improvement for you. Send the data center location to [email protected]. Microsoft uses your feedback for expansion plans.
-
-Microsoft is working on additional capabilities to improve latency. As soon as these improvements are available, the documentation will be updated.
-
 ## Next steps
 [Work with existing on-premises proxy servers](application-proxy-configure-connectors-with-proxy-servers.md)

articles/active-directory/app-proxy/application-proxy-troubleshoot.md

@@ -77,10 +77,6 @@ This list covers errors that your end users might encounter when they try to acc
 | A server with the specified host name could not be found. | Your user may get this error when trying to access the app you published if the application's custom domain is not configured correctly. Make sure you've uploaded a certificate for the domain and configured the DNS record correctly by following the steps in [Working with custom domains in Azure AD Application Proxy](./application-proxy-configure-custom-domain.md) |
 |Forbidden: This corporate app can't be accessed OR The user could not be authorized. Make sure the user is defined in your on-premises AD and that the user has access to the app in your on-premises AD. | This could be a problem with access to authorization information, see [Some applications and APIs require access to authorization information on account objects]( https://support.microsoft.com/help/331951/some-applications-and-apis-require-access-to-authorization-information). In a nutshell, add the app proxy connector machine account to the "Windows Authorization Access Group" builtin domain group to resolve. |
 
-## My error wasn't listed here
-
-If you encounter an error or problem with Azure AD Application Proxy that isn't listed in this troubleshooting guide, we'd like to hear about it. Send an email to our [feedback team](mailto:[email protected]) with the details of the error you encountered.
-
 ## See also
 * [Enable Application Proxy for Azure Active Directory](application-proxy-add-on-premises-application.md)
 * [Publish applications with Application Proxy](application-proxy-add-on-premises-application.md)