Merge branch 'master' of https://github.com/Microsoftdocs/azure-docs-pr into funlanding

Author: TerryLanfear

articles/active-directory/saas-apps/hackerone-tutorial.md

@@ -104,7 +104,7 @@ To configure Azure AD single sign-on with HackerOne, perform the following steps
     ![HackerOne Domain and URLs single sign-on information](common/sp-identifier.png)
 
 	a. In the **Sign on URL** text box, enter the following:
-    `https://hackerone.com/users/saml/auth`
+    `https://hackerone.com/users/saml/sign_in?email=<configured domain>`
 
     b. In the **Identifier (Entity ID)** text box, enter the following:
     `hackerone.com`
@@ -153,7 +153,13 @@ To configure Azure AD single sign-on with HackerOne, perform the following steps
 
     a. Click **Run test**.
 
-    b. If the value of the **Status** field equals **Last test status: created**, contact your [HackerOne support team](mailto:[email protected]) to request a review of your configuration.
+6. When the test finishes successfully and the **Status** field shows **Last test status: success**, select the **Request Verification** button to submit to HackerOne for approval.
+
+    ![Submit to HackerOne for approval](./media/hackerone-tutorial/tutorial-hackerone-006.png)
+
+7. After HackerOne approves the settings, you can select the **Migrate Users** button to require SSO authentication for all users.
+
+    ![Enable SAML](./media/hackerone-tutorial/tutorial-hackerone-007.png)
 
 ### Create an Azure AD test user
 
@@ -172,7 +178,7 @@ The objective of this section is to create a test user in the Azure portal calle
     ![The User dialog box](common/user-properties.png)
 
     a. In the **Name** field enter **BrittaSimon**.
-  
+
     b. In the **User name** field type **brittasimon\@yourcompanydomain.extension**  
     For example, [email protected]
 

articles/active-directory/saas-apps/media/hackerone-tutorial/tutorial-hackerone-006.png

@@ -22,7 +22,7 @@ This article uses the [Azure portal](https://portal.azure.com) and Azure CLI to
 |-|-|-|-|
 | Application logging | Windows, Linux | App Service file system and/or Azure Storage blobs | Logs messages generated by your application code. The messages can be generated by the web framework you choose, or from your application code directly using the standard logging pattern of your language. Each message is assigned one of the following categories: **Critical**, **Error**, **Warning**, **Info**, **Debug**, and **Trace**. You can select how verbose you want the logging to be by setting the severity level when you enable application logging.|
 | Web server logging| Windows | App Service file system or Azure Storage blobs| Raw HTTP request data in the [W3C extended log file format](/windows/desktop/Http/w3c-logging). Each log message includes data such as the HTTP method, resource URI, client IP, client port, user agent, response code, and so on. |
-| Detailed error logging | Windows | App Service file system | Copies of the *.htm* error pages that would have been sent to the client browser. For security reasons, detailed error pages shouldn't be sent to clients in production, but App Service can save the error page each time an application error occurs that has HTTP code 400 or greater. The page may contain information that can help determine why the server returns the error code. |
+| Detailed Error Messages| Windows | App Service file system | Copies of the *.htm* error pages that would have been sent to the client browser. For security reasons, detailed error pages shouldn't be sent to clients in production, but App Service can save the error page each time an application error occurs that has HTTP code 400 or greater. The page may contain information that can help determine why the server returns the error code. |
 | Failed request tracing | Windows | App Service file system | Detailed tracing information on failed requests, including a trace of the IIS components used to process the request and the time taken in each component. It's useful if you want to improve site performance or isolate a specific HTTP error. One folder is generated for each failed request, which contains the XML log file, and the XSL stylesheet to view the log file with. |
 | Deployment logging | Windows, Linux | App Service file system | Logs for when you publish content to an app. Deployment logging happens automatically and there are no configurable settings for deployment logging. It helps you determine why a deployment failed. For example, if you use a [custom deployment script](https://github.com/projectkudu/kudu/wiki/Custom-Deployment-Script), you might use deployment logging to determine why the script is failing. |
 

articles/active-directory/saas-apps/media/hackerone-tutorial/tutorial-hackerone-007.png

@@ -0,0 +1,28 @@
+---
+title: How to configure OpenSSL for Linux
+titleSuffix: Azure Cognitive Services
+description: Learn how to configure OpenSSL for Linux.
+services: cognitive-services
+author: jhakulin
+manager: nitinme
+ms.service: cognitive-services
+ms.subservice: speech-service
+ms.topic: conceptual
+ms.date: 01/15/2020
+ms.author: jhakulin
+---
+
+# Configure OpenSSL for Linux
+
+OpenSSL is dynamically configured to the host-system version when using any Speech SDK release version prior to 1.9.0.
+
+Starting at the Speech SDK version 1.9.0 and onwards, OpenSSL (version 1.1.1b) is statically linked to the Speech SDK core library.
+
+## Troubleshoot connectivity
+
+In case of connection failures with 1.9.0 release, please check that OpenSSL `ssl/certs` directory exists in `/usr/lib` directory under the Linux system. If `ssl/certs` does not exist, please check where OpenSSL is installed in your system (using `which openssl` command), and locate openssl `certs`directory and copy the content of that directory into `/usr/lib/ssl/certs` directory.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Check the general overview about the Speech SDK capabilities and supported platforms](speech-sdk.md)

articles/app-service/troubleshoot-diagnostic-logs.md

@@ -66,7 +66,7 @@ class Program
         // Edit with your desired region for `{region}`
         var response = await client.PostAsync($"https://signature.{region}.cts.speech.microsoft.com/api/v1/Signature/GenerateVoiceSignatureFromFormData", form);
         // A voice signature contains Version, Tag and Data key values from the Signature json structure from the Response body.
-        // Voice signature format example: { "Version": <Numeric value>, "Tag": "string", "Data": "string" }
+        // Voice signature format example: { "Version": <Numeric string or integer value>, "Tag": "string", "Data": "string" }
         var jsonData = await response.Content.ReadAsStringAsync();
     }
 
@@ -85,7 +85,7 @@ class Program
         // Edit with your desired region for `{region}`
         var response = await client.PostAsync($"https://signature.{region}.cts.speech.microsoft.com/api/v1/Signature/GenerateVoiceSignatureFromByteArray", content);
         // A voice signature contains Version, Tag and Data key values from the Signature json structure from the Response body.
-        // Voice signature format example: { "Version": <Numeric value>, "Tag": "string", "Data": "string" }
+        // Voice signature format example: { "Version": <Numeric string or integer value>, "Tag": "string", "Data": "string" }
         var jsonData = await response.Content.ReadAsStringAsync();
     }
 
@@ -108,6 +108,7 @@ Sample code highlights include:
 - Registering the events of interest
 - Adding or removing participants to the conversation using the Conversation object
 - Streaming the audio
+- In Speech SDK version 1.9.0 and onwards both `int` and `string` value types are supported in the voice signature version field.
 
 The transcription and speaker identifier come back in the registered events.
 
@@ -184,7 +185,7 @@ public class MyConversationTranscriber
                     // Add participants to the conversation.
                     // Create voice signatures using REST API described in the earlier section in this document.
                     // Voice signature needs to be in the following format:
-                    // { "Version": <Numeric value>, "Tag": "string", "Data": "string" }
+                    // { "Version": <Numeric string or integer value>, "Tag": "string", "Data": "string" }
 
                     var speakerA = Participant.From("Speaker_A", "en-us", signatureA);
                     var speakerB = Participant.From("Speaker_B", "en-us", signatureB);

articles/cognitive-services/Speech-Service/how-to-configure-openssl-linux.md

@@ -452,7 +452,9 @@
       href: how-to-use-logging.md
     - name: How to track memory usage
       href: how-to-track-speech-sdk-memory-usage.md
-      displayName: "memory usage, memory consumption, object logging, object tracking, memory"
+    - name: How to configure OpenSSL for Linux
+      href: how-to-configure-openssl-linux.md
+      displayName: "memory usage, memory consumption, object logging, object tracking, memory, openssl"
   - name: Samples
     items:
     - name: Speech SDK Samples (GitHub)