pull base content,head:MicrosoftDocs:main,into:wwlpublishsync

Author: wwlpublish

learn-pr/advocates/improve-reliability-scaling/2-definition.yml

@@ -17,18 +17,6 @@ quiz:
   title: Check your knowledge
   questions:
 
-  - content: 'Making your application or service more scalable can also make it:'
-    choices:
-    - content: 'less complex'
-      isCorrect: false
-      explanation: "With scaling, especially when scaling out, there's often an increase in complexity."
-    - content: 'more reliable'
-      isCorrect: true
-      explanation: 'Correct.'
-    - content: 'easier to troubleshoot'
-      isCorrect: false
-      explanation: 'Because (especially when scaling out) there are more moving parts, it may not be easier to troubleshoot.'
-
   - content: 'Making your application or service more scalable can also make it:'
     choices:
     - content: 'less complex'

learn-pr/wwl-azure/find-commands-get-help-windows-powershell/includes/2-define-modules-powershell.md

@@ -1,5 +1,11 @@
 *Modules* are groups of related PowerShell capabilities that are bundled together into a single unit. For the purposes of this class, you can think of them as containers hosting multiple cmdlets. Modules help with organizing cmdlets into distributable units. Microsoft and other software companies provide modules as part of the management tools for their applications and services.
 
+You can check the list of available modules by running the following command:
+
+```powershell
+Get-Module -ListAvailable
+```
+
 To use a module's cmdlets, the module must be loaded into the current PowerShell session. This typically takes place automatically but, depending on your configuration, might require that you load modules explicitly by running the **Import-Module** cmdlet. Some server products, such as Microsoft Exchange Server, provide a shortcut to what appears to be a dedicated management shell. However, this is really a normal PowerShell console session with application-specific modules already loaded.
 
 ## Autoloading
@@ -8,7 +14,11 @@ In Windows PowerShell version 3.0 and newer, modules load automatically if you r
 
 For PowerShell 7, the **PSModulePath** includes the following locations:
 
-`C:\Users\<user>\Documents\PowerShell\Modules` `C:\Program Files\PowerShell\Modules` `C:\Program Files\PowerShell\7\Modules` `C:\Program Files\WindowsPowerShell\Modules` `C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules`
+- `C:\Users\<user>\Documents\PowerShell\Modules` 
+- `C:\Program Files\PowerShell\Modules` 
+- `C:\Program Files\PowerShell\7\Modules` 
+- `C:\Program Files\WindowsPowerShell\Modules` 
+- `C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules`
 
 > [!NOTE]
 > When using Windows PowerShell, the path **%systemdir%\\WindowsPowerShell\\v1.0\\Modules** is commonly referred to by using the combination of the `$PSHome` environment variable (which points to **%systemdir%\\WindowsPowerShell\\v1.0**) and the **Modules** path (that is, by using the `$PSHome\Modules` notation). For PowerShell 7.0, the `$PSHome` environment variable refers to **C:\\Program Files\\PowerShell\\7**.

learn-pr/wwl-azure/find-commands-get-help-windows-powershell/includes/5-use-show-command-powershell.md

@@ -2,11 +2,15 @@ The **Show-Command** cmdlet opens a window that displays either a list of comman
 
 To display a specific command's parameters, provide the name of the command as the value for the *‑Name* parameter. For example, to open the **Show** **Command Window** with the command used to retrieve an Active Directory user, enter the following command in the console, and then press the Enter key:
 
-`Show-Command –Name Get-ADUser`
+```powershell
+Show-Command –Name Get-ADUser
+```
 
 The *–Name* parameter is positional, so the following command produces the same result:
 
-`Show-Command Get-ADUser`
+```powershell
+Show-Command Get-ADUser
+```
 
 If you select the **Show** **Command Window** option in the ISE, and your cursor is within or immediately next to a command name within the console or scripting pane, the results are the same.
 
@@ -25,7 +29,9 @@ Windows PowerShell provides extensive in-product help for commands. You can acce
 
 For example, to display the help information for the **Get-ChildItem** cmdlet, enter the following command in the console, and then press the Enter key:
 
-`Get-Help Get-ChildItem`
+```powershell
+Get-Help Get-ChildItem
+```
 
 ### Get-Help parameters
 

learn-pr/wwl-azure/review-windows-powershell/includes/2-learn-about-windows-powershell.md

@@ -62,6 +62,9 @@ The following table provides a general timeline of the major PowerShell releases
 
 | Version        | Release Date | Notes                                                        |
 | -------------- | ------------ | ------------------------------------------------------------ |
+| PowerShell 7.5 | January 2025     | Built on .NET 9.0.                                           |
+| PowerShell 7.4 | November 2023     | Built on .NET 8.0.                                           |
+| PowerShell 7.3 | November 2022     | Built on .NET 7.0.                                           |
 | PowerShell 7.2 | November 2021     | Built on .NET 6.0.                                           |
 | PowerShell 7.1 | November 2020     | Built on .NET 5.0.                                           |
 | PowerShell 7.0 | March 2020     | Built on .NET Core 3.1.                                      |
@@ -74,7 +77,7 @@ The following table provides a general timeline of the major PowerShell releases
 | PowerShell 1.0 | November 2006     | Installable on Windows XP SP2, Windows Server 2003 SP1, and Windows Vista. Optional component of Windows Server 2008. |
 
 > [!NOTE]
-> Throughout this module, topics will relate to both the latest Windows PowerShell and PowerShell versions (5.1 and 7.2). Most cmdlets will work using either platform. However, there'll be a note if a specific feature is only supported or relates to one specific platform.
+> Throughout this module, topics will relate to both the latest Windows PowerShell and PowerShell versions (5.1 and 7.5). Most cmdlets will work using either platform. However, there'll be a note if a specific feature is only supported or relates to one specific platform.
 
 > **Additional reading:** To support more recent versions of PowerShell on down-level operating systems, you might need to install the latest version of the Windows Management Framework. For more information, refer to [Install and Configure WMF 5.1](https://aka.ms/install-and-configure-WMF-5.1).
 

learn-pr/wwl-azure/review-windows-powershell/includes/4-identify-factors-install-use-windows-powershell.md

@@ -36,7 +36,9 @@ The execution policy in PowerShell is meant to minimize the possibility of a use
 
 To identify the effective execution policy for the current PowerShell session, use the following cmdlet:
 
-`Get-ExecutionPolicy`
+```powershell
+Get-ExecutionPolicy
+```
 
 You can configure the following policy settings:
 
@@ -49,4 +51,8 @@ You can configure the following policy settings:
 
 To change the execution policy in PowerShell, use the following command:
 
-`Set-ExecutionPolicy -ExecutionPolicy <PolicyName>`
+```powershell
+Set-ExecutionPolicy -ExecutionPolicy <PolicyName>
+```
+
+

learn-pr/wwl-azure/review-windows-powershell/includes/6-configure-integrated-scripting-environment.md

@@ -15,4 +15,7 @@ Other ISE features include:
 - Integration with Windows PowerShell’s debugging capabilities.
 
 > [!NOTE]
-> The Windows PowerShell ISE is available on Windows OS, but it won't work with PowerShell 6 and newer. For a similar experience, you can use Visual Studio Code (VS Code) with the PowerShell extension. You will learn more about it in the next unit of this module. 
+> The PowerShell ISE is no longer in active feature development. As a shipping component of Windows, it continues to be officially supported for security and high-priority servicing fixes. We currently have no plans to remove the ISE from Windows.
+Windows PowerShell ISE won't work with PowerShell 6 and newer. For a similar experience, you can use Visual Studio Code (VS Code) with the PowerShell extension. You will learn more about it in the next unit of this module. 
+
+

learn-pr/wwl-azure/understand-command-syntax-windows-powershell/includes/2-discover-structure-of-powershell-cmdlets.md

@@ -13,6 +13,10 @@ The verb portion of a cmdlet name indicates what the cmdlet does. There's a set
 - **Add**. Adds a resource to a container of multiple resources.
 - **Remove**. Deletes a resource from a container of multiple resources.
 
+> [!NOTE]
+>You can run the `Get-Verb` command to have the full list of approved verbs.
+
+
 This list represents just some of the verbs that cmdlets use. Additionally, some verbs perform similar functions. For example, the **Add** verb can create a resource, similar to the **New** verb. Some verbs might seem similar, but have different functions. For example, the **Read** verb retrieves information that a resource contains, such as a text file's content, whereas the **Get** verb retrieves the actual file.
 
 ## Cmdlet nouns

learn-pr/wwl-azure/understand-command-syntax-windows-powershell/includes/5-display-about-files-content-powershell.md

@@ -1,6 +1,23 @@
 Although much of the help content in Windows PowerShell relates to commands, there are also many help files that describe PowerShell concepts. These files include information about the PowerShell scripting language, operators, and other details. This information doesn't specifically relate to a single command, but to global shell techniques and features.
 
-You can review a complete list of these topics by running **Get-Help about\***, and then reviewing a single topic by running **Get-Help about\_topicname**. An example is **Get-Help about\_common\_parameters**. These commands don't use the *–Example* or *–Full* parameters of the **Help** command. However, they're compatible with the *–ShowWindow* and *–Online* parameters.
+You can review a complete list of these topics by running:
+
+```powershell
+Get-Help about*
+```
+
+To view a specific topic, use:
+
+```powershell
+Get-Help about_common_parameters
+```
+
+You can also open the help topic in a separate window or online:
+
+```powershell
+Get-Help about_common_parameters -ShowWindow
+Get-Help about_common_parameters -Online
+```
 
 When you use wildcard characters with the **Get-Help** command, **About** help files will appear in a list when their titles contain a match for your wildcard pattern. Typically, **About** help files will appear last, after any commands whose names also matched your wildcard pattern. You can also use the *‑Category* parameter to specify a search for **About** files.
 

learn-pr/wwl-data-ai/fundamentals-generative-ai/includes/3b-use-language-models.md

@@ -1,6 +1,4 @@
-Today, importantly, developers do not need to train models from scratch. To build a generative AI application, you can use pre-trained models. Some language models are open-source and publicly available. Others are offered in proprietary catalogs. Different models exist today which mostly differ by the specific data they've been trained on, or by how they implement attention within their architectures. Language models power the 'app logic' component of the interaction between users and generative AI applications. 
-
-![Diagram of an application.](../media/application-logic-image.png)
+Today, importantly, developers don't need to train models from scratch. To build a generative AI application, you can use pretrained models. Some language models are open-source and publicly available. Others are offered in proprietary catalogs. Different models exist today which mostly differ by the specific data used to train them, or by how they implement attention within their architectures. 
 
 ## Large and small language models
 In general, language models can be considered in two categories: *Large Language Models* (LLMs) and *Small Language models* (SLMs).
@@ -9,6 +7,6 @@ In general, language models can be considered in two categories: *Large Language
 |-|-|
 |LLMs are trained with vast quantities of text that represents a wide range of general subject matter – typically by sourcing data from the Internet and other generally available publications.| SLMs are trained with smaller, more subject-focused datasets|
 |When trained, LLMs have many billions (even trillions) of parameters (weights that can be applied to vector embeddings to calculate predicted token sequences).|Typically have fewer parameters than LLMs.|
-|Able to exhibit comprehensive language generation capabilities in a wide range of conversational contexts.|This focused vocabulary makes them very effective in specific conversational topics, but less effective at more general language generation.|
+|Able to exhibit comprehensive language generation capabilities in a wide range of conversational contexts.|This focused vocabulary makes them effective in specific conversational topics, but less effective at more general language generation.|
 |Their large size can impact their performance and make them difficult to deploy locally on devices and computers.|The smaller size of SLMs can provide more options for deployment, including local deployment to devices and on-premises computers; and makes them faster and easier to fine-tune.|
-|Fine-tuning the model with additional data to customize its subject expertise can be time-consuming, and expensive in terms of the compute power required to perform the additional training.|Fine-tuning can potentially be less time-consuming and expensive.|
+|Fine-tuning the model with more data to customize its subject expertise can be time-consuming, and expensive in terms of the compute power required to perform the extra training.|Fine-tuning can potentially be less time-consuming and expensive.|

learn-pr/wwl-data-ai/get-started-generative-ai-azure/1-introduction.yml

@@ -0,0 +1,20 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.get-started-generative-ai-azure.introduction
+title: Introduction
+metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Introduction
+  description: Introduction 
+  author: sherzyang
+  ms.author: sheryang
+  ms.date: 05/26/2025
+  ms.topic: unit
+  ms.collection:
+    - wwl-ai-copilot
+durationInMinutes: 2
+content: |
+  [!include[](includes/1-introduction.md)]
+
+
+