merge main updates from upstream

.github/workflows/script-cleanup.yml

@@ -0,0 +1,54 @@
+name: Daily RG Cleanup
+
+on:
+  schedule:
+    # runs every day at 11:11 UTC
+    - cron: '11 11 * * *'
+  workflow_dispatch:
+
+permissions:
+    contents: write
+    id-token: write
+    issues: write
+
+jobs:
+  cleanup:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Az CLI login'
+        uses: azure/login@v1
+        with:
+            client-id: ${{ secrets.AZURE_CLIENT_ID }}
+            tenant-id: ${{ secrets.AZURE_TENANT_ID }}
+            subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
+
+      - name: Install jq
+        run: sudo apt-get update && sudo apt-get install -y jq
+
+      - name: Cleanup Resource Groups
+        run: |
+          echo "Fetching all resource groups in the subscription..."
+          rgs_json=$(az group list --output json)
+
+          # don't exit on errors in this block
+          set +e
+
+          echo "Attempting to delete all resource groups except 'exec-docs-ai' and those containing 'mcp'..."
+          echo "$rgs_json" |
+            jq -r '.[] | select(.name != "exec-docs-ai" and (.name | contains("mcp") | not)) | .name' |
+            while read -r rg_name; do
+              if [[ -z "$rg_name" ]]; then
+                echo "Skipping empty resource group name."
+                continue
+              fi
+              echo -n "Deleting $rg_name… "
+              az group delete \
+                --name "$rg_name" \
+                --yes \
+                --no-wait \
+                && echo "OK" \
+                || echo "⚠️ Skipped (deny-assignment or other error)"
+            done
+
+          # restore "exit on error" if you need it later
+          set -e

.github/workflows/sync.yml

@@ -1,8 +1,8 @@
 name: Sync Markdown Files
 
 on:
-  schedule:
-    - cron: '0 15 * * *' 
+  # schedule:
+  #   - cron: '0 15 * * *' 
   workflow_dispatch:
 
 permissions:

.gitignore

@@ -6,4 +6,5 @@ _themes*/
 _repo.*/
 
 .openpublishing.buildcore.ps1
-ie.log
+ie.log
+report.json

README.md

@@ -8,6 +8,7 @@ These experiences utilize [Innovation Engine](https://github.com/Azure/Innovatio
 
 ## Table of Contents
 
+- [Selecting Documentation for Exec Docs](#selecting-documentation-for-exec-docs)
 - [How to Write an Exec Doc](#how-to-write-an-exec-doc)
     - [Training Resources (Optional)](#training-resources-optional)
     - [Setup](#setup)
@@ -18,6 +19,82 @@ These experiences utilize [Innovation Engine](https://github.com/Azure/Innovatio
 - [Frequently Asked Questions (FAQs)](#frequently-asked-questions-faqs)
 - [Contact Information for Exec Docs](#contact-information-for-exec-docs)
 
+I'll update the highlighted section with the clarified information about command execution limitations:
+
+## Selecting Documentation for Exec Docs
+
+Not all documentation is suitable for conversion to Exec Docs. Use these filters to determine if a document can be effectively converted:
+
+1. **Command Execution Limitations**
+   - **Supported scenarios:**
+     - Any command that can run in a BASH terminal (e.g. azurecli, azure-cli-interactive, azurecli-interactive commands)
+
+   - **Not supported currently:**
+     - PowerShell scripts
+     - GUI-based instructions
+     - Commands requiring `sudo` privileges
+     - Direct code blocks of languages that aren't bash/shell commands
+
+   **Example of supported command:**
+   ```markdown
+        ```bash
+        export REGION="eastus"
+        export RESOURCE_GROUP="myResourceGroup"
+        az group create --name $RESOURCE_GROUP --location $REGION
+        ```
+   ```
+
+   **Example of unsupported command (SQL query below won't work):**
+   ```markdown
+        ```sql
+        INSERT INTO myTable (name, value) VALUES ('test', 123);
+        ```
+   ```
+
+   **Example of supported command (SQL query below will work):**
+   ```markdown
+        ```bash
+        export DATABASE_NAME="mydb"
+        export TABLE_NAME="myTable"
+        psql -d $DATABASE_NAME -c "INSERT INTO $TABLE_NAME (name, value) VALUES ('test', 123);"
+        ```
+   ```
+   >**Note:** You can include code blocks of any type in your documentation for human readers, but only the types listed above in the "Supported Code Block Types" section will be executed by Innovation Engine. Other code block types will be displayed but ignored during execution.
+
+   >**Note:** The key principle is simple: if you can run it in a BASH terminal as written, it will work with Exec Docs (although at this time `sudo` is not supported). Code blocks in other languages won't be executed directly but can be included for human readers. 
+
+2. **Azure Portal Custom Cloud Shell Constraints**
+    - **Supported scenarios:**
+        - Standard Azure resource operations (create, read, update, delete)
+        - Commands running within the user's subscription scope
+        - Standard service deployments (VMs, storage, networking)
+
+    - **Not supported currrently:**
+        - Commands requiring elevated Microsoft Graph API permissions
+        - Operations needing KeyVault special access
+        - Cross-subscription or tenant-level operations
+        - Commands requiring admin consent
+
+   **Example of supported command:**
+   ```markdown
+        ```bash
+        export RESOURCE_GROUP="myResourceGroup"
+        export LOCATION="eastus"
+        az group create --name $RESOURCE_GROUP --location $LOCATION
+        ```
+   ```
+
+   **Example of unsupported command:**
+   ```markdown
+        ```bash
+        export APP_NAME="myApp"
+        # This requires elevated Graph API permissions and would fail
+        az ad app create --display-name $APP_NAME --native-app
+        ```
+   ```
+
+This filter system ensures that you select documentation that can be effectively transformed into executable docs that provide value through automated deployment capabilities. Please reach out to the [Exec Docs Team](#contact-information-for-exec-docs) if you have any questions about the suitability of a document for conversion to an Exec Doc.
+
 ## How to Write an Exec Doc
 
 Follow these steps in sequence to write an Exec Doc either by converting an existing Azure Doc i.e. building on top of the author's work or from scratch i.e. you are the author _(read the Notes in any step for more information)_:
@@ -81,33 +158,14 @@ Check if all prerequisites below are met before writing the Exec Doc. ***If any
     │       └── my-script.yaml 
     ``` 
 
-6. Code blocks are used to provide examples, commands, or other code snippets in Exec Docs. They are distinguished by a triple backtick (```) at the start and end of the block. 
-
-    Ensure that the Exec Doc contains at least 1 code block and every input code block's type in the Exec Doc is taken from this list: 
-
-    - bash 
-    - azurecli
-    - azure-cli-interactive 
-    - azurecli-interactive  
-
-    **Example:** 
-
-    ```bash 
-    az group create --name $MY_RESOURCE_GROUP_NAME --location $REGION 
-    ``` 
-
-    >**Note:** This rule does not apply to output code blocks, which are used to display the results of commands, scripts, or other operations. These blocks help in illustrating what the expected output should look like. They include, but are not limited to, the following types: _output, json, yaml, console, text, and log._
-
-    >**Note:** While Innovation Engine can _parse_ a code block of any type, given its current features, it can only _execute_ code blocks of the types above. So, it is important to ensure that the code blocks in your Exec Doc are of the types above. 
-
-7. Headings are used to organize content in a document. The number of hashes indicates the level of the heading. For example, a single hash (#) denotes an h1 heading, two hashes (##) denote an h2 heading, and so on. Innovation Engine uses headings to structure the content of an Exec Doc and to provide a clear outline of the document's contents. 
+6. Headings are used to organize content in a document. The number of hashes indicates the level of the heading. For example, a single hash (#) denotes an h1 heading, two hashes (##) denote an h2 heading, and so on. Innovation Engine uses headings to structure the content of an Exec Doc and to provide a clear outline of the document's contents. 
 
     Ensure there is at least one h1 heading in the Exec Doc, denoted by a single hash (#) at the start of the line. 
 
     **Example:** 
 
     ```markdown 
-    # Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using Azure CLI 
+        # Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using Azure CLI 
     ``` 
 
 ### Writing Requirements
@@ -299,15 +357,22 @@ Check if all prerequisites below are met before writing the Exec Doc. ***If any
 
         **Example:**
 
-        **Title:** _Making your Azure Doc executable!_
+        **Title:** Making your Azure Doc executable!
 
-        _**Details:** Hello [author_name], \
-        \
-        I am submitting this PR to make the doc you have authored executable! Essentially, without any major content changes, this will make your doc accesssible, accurate, and actionable! And what is "this": Exec Docs (short for Executable Documentation) \
-        \
-        Exec Docs are documents that automate the deployment/maintenace of Azure resources using Azure CLI commands. This is a new initiative undertaken by the Azure Core Linux, Skilling, and Portal teams to simplify the evaluation and adoption of services for Linux on Azure customers. [Learn More Here!](https://github.com/MicrosoftDocs/executable-docs/blob/main/README.md)\
-        \
-        Once you get acquainted with Exec Docs, I would love to get your review on this doc. If you have any questions feel free to contact me or [Naman Parikh](mailto:[email protected])._
+        **Details:**
+
+      Hello [author_name],
+
+      This PR will increase the value of the doc to customers, it turns the doc into an Executable Document! An Executable Document improves the customer experience by making the content actionable in portal as well as ensuring that it works, as documented, using automated testing. 
+
+      Exec Docs are:
+      - Fully integrated into Portal where the user can leverage them in hands on learning experiences OR low effort "click to deploy" scenarios
+      - Increased reusability through adoption of consistent best practices and exportable scripts
+      - Higher quality as a result of automated testing 
+
+      We have conducted many experiments and have consistent results that show higher CSAT from customers working with Exec Docs. This in turn results in a higher conversion rate from experimentation to paid customer. [Learn More Here!](https://microsoft-my.sharepoint.com/:p:/p/namanparikh/EdxlQiyhGDhFmGcAUE9fejYB3r6ZzgLqWO3jZPK7fcnKgQ?e=CDWOet) 
+
+      Once you get acquainted with Exec Docs, I would love to get your review on this doc. If you have any questions feel free to contact me or [Naman Parikh](mailto:[email protected]).
 
     - Assign the original Exec Doc author (if it is not you) as a reviewer to the PR. In most cases, this assignment should happen automatically and should include a reviewer from the Skilling team.
     - Add the comment ***#sign-off***  in the PR comments section once the Exec Doc is successfully reviewed. This will trigger the automated pipeline to merge the PR into the public repo.
@@ -349,12 +414,12 @@ Check if all prerequisites below are met before writing the Exec Doc. ***If any
 
         **Deeplink Template:**
         ```markdown
-        [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://ms.portal.azure.com/#view/Microsoft_Azure_CloudNative/SubscriptionSelectionPage.ReactView/isLearnMode~/true/referer/docs/tutorialKey/<add_file_path_of_Exec_Doc>)
+            [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://ms.portal.azure.com/#view/Microsoft_Azure_CloudNative/SubscriptionSelectionPage.ReactView/isLearnMode~/true/referer/docs/tutorialKey/<add_file_path_of_Exec_Doc>)
         ```
 
         **Deeplink for Example Exec Doc:**
         ```markdown
-        [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://ms.portal.azure.com/#view/Microsoft_Azure_CloudNative/SubscriptionSelectionPage.ReactView/isLearnMode~/true/referer/docs/tutorialKey/azure-docs%2farticles%2faks%2fquick-kubernetes-deploy-cli.md)
+            [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://ms.portal.azure.com/#view/Microsoft_Azure_CloudNative/SubscriptionSelectionPage.ReactView/isLearnMode~/true/referer/docs/tutorialKey/azure-docs%2farticles%2faks%2fquick-kubernetes-deploy-cli.md)
         ```
 
         **Example of Button in Live Exec Doc:**
@@ -456,11 +521,10 @@ For the first PR, if either the original doc author or someone from skilling is
 ## Contact Information for Exec Docs
 
 - PM for Exec Docs E2E Experience: [Naman Parikh](mailto:[email protected])
-- PM for Exec Docs Portal Experience: [Varun Desai](mailto:[email protected])
-- PM for Innovation Engine: [Mitchell Bifeld](mailto:[email protected])
-- Skilling & Content Developer for Exec Docs: [Carol Smith](mailto:[email protected])
-- Devs for Exec Docs: [PJ Singh](mailto:[email protected]), [Aria Amini](mailto:[email protected]), [Abhishek Bhombore](mailto:[email protected])
-- Devs for Innovation Engine: [Vincenzo Marcella](mailto:[email protected]), [Rahul Gupta](mailto:[email protected])
+- PM for Exec Docs Portal Experience: [Matt DePietro]([email protected])
+- PM for Innovation Engine: [Ross Gardler](mailto:[email protected])
+- MS Learn Point Person: [Carol Smith](mailto:[email protected]), [Rayo Flores](mailto:[email protected]), [Chase Dovey](mailto:[email protected]),  
+- Devs for Exec Docs: [PJ Singh](mailto:[email protected]), [Aria Amini](mailto:[email protected])
 
 ## Trademarks
 This project may contain trademarks or logos for projects, products, or