Merge pull request #286761 from vvs11/main

Added note for users in the docs

Author: prmerger-automator[bot]

articles/playwright-testing/includes/include-playwright-portal-create-workspace.md

@@ -12,7 +12,7 @@ ms.date: 10/04/2023
 
     > [!TIP]
     > If you have multiple workspaces, you can switch to another workspace by selecting the workspace name at the top of the page, and then select **Manage all workspaces**.
-
+    
 1. If you don't have a workspace yet, select **+ New workspace**, and then provide the following information:
 
     |Field  |Description  |

articles/playwright-testing/quickstart-automate-end-to-end-testing.md

@@ -164,6 +164,9 @@ Update the CI workflow definition to run your Playwright tests with the Playwrig
 
     When the CI workflow is triggered, your Playwright tests run in your Microsoft Playwright Testing workspace on cloud-hosted browsers, across 20 parallel workers.
 
+> [!NOTE]
+> Reporting feature will be enabled by default for existing workspaces. This is being rolled out in stages and will take a few days. To avoid failures, confirm that `Rich diagnostics using reporting` setting is ON for your workspace before proceeding. See, [Enable reporting for workspace](./how-to-use-service-features.md#manage-feature-for-the-workspace).
+
 > [!CAUTION]
 > With Microsoft Playwright Testing, you get charged based on the number of total test minutes and test result published. If you're a first-time user or [getting started with a free trial](./how-to-try-playwright-testing-free.md), you might start with running a single test at scale instead of your full test suite to avoid exhausting your free test minutes and test results.
 >

articles/playwright-testing/quickstart-run-end-to-end-tests.md

@@ -113,7 +113,10 @@ You've now prepared the configuration for running your Playwright tests in the c
 
 ### Run a single test at scale
 
-With Microsoft Playwright Testing, you get charged based on the number of total test minutes and number of test results published. If you're a first-time user or [getting started with a free trial](./how-to-try-playwright-testing-free.md), you might start with running a single test at scale instead of your full test suite to avoid exhausting your free test minutes.
+With Microsoft Playwright Testing, you get charged based on the number of total test minutes and number of test results published. If you're a first-time user or [getting started with a free trial](./how-to-try-playwright-testing-free.md), you might start with running a single test at scale instead of your full test suite to avoid exhausting your free trial limits.
+
+> [!NOTE]
+> Reporting feature will be enabled by default for existing workspaces. This is being rolled out in stages and will take a few days. To avoid failures, confirm that `Rich diagnostics using reporting` setting is ON for your workspace before proceeding. See, [Enable reporting for workspace](./how-to-use-service-features.md#manage-feature-for-the-workspace).
 
 After you validate that the test runs successfully, you can gradually increase the test load by running more tests with the service.
 
@@ -249,6 +252,8 @@ The test run contains the CI information, test run status, workers used, duratio
 > [!TIP]
 > You can use Microsoft Playwright Testing service features independently. You can publish test results to the portal without using the cloud-hosted browsers feature and you can also use only cloud-hosted browsers to expedite your test suite without publishing test results. 
 
+> [!NOTE]
+> The test results and artifacts that you publish are retained on the service for 90 days. After that, they are automatically deleted.  
 
 ## Optimize parallel worker configuration