Merge pull request MicrosoftDocs#276 from msewaweru/sdk-v2-doc-updates

Updated the get-started articles as per SDK v2 changes

Author: timayabi2020

microsoftgraph/docs-conceptual/authentication-commands.md

@@ -39,9 +39,11 @@ There are three ways to allow delegated access using `Connect-MgGraph`:
     Connect-MgGraph -AccessToken $AccessToken
     ```
 
-### App-only access via client credential with a certificate
+### App-only access
 
-To use app-only access, the certificate is loaded from *Cert:\CurrentUser\My\\* when `-CertificateThumbprint` or `-CertificateName` is specified. Make sure that the certificate you're using is present in the store before calling `Connect-MgGraph`. For more info, see [Use app-only authentication with the Microsoft Graph PowerShell SDK](app-only.md).
+#### Using client credential with a certificate
+
+To use app-only access, the certificate is loaded from either *Cert:\CurrentUser\My\\* or *Cert:\LocalMachine\My\\* when `-CertificateThumbprint` or `-CertificateName` is specified. Make sure that the certificate you're using is present in either certificate store before calling `Connect-MgGraph`. For more info, see [Use app-only authentication with the Microsoft Graph PowerShell SDK](app-only.md).
 
 - Using Certificate Thumbprint:
 
@@ -64,6 +66,36 @@ To use app-only access, the certificate is loaded from *Cert:\CurrentUser\My\\*
 
     To use a certificate stored in your machine's certificate store or another ___location when connecting to Microsoft Graph, specify the certificate's ___location.
 
+#### Using client secret credentials
+
+If you need interactions in the background, without a user to sign in, this type of grant will help you. Support for client secret credentials was added by adding **-ClientSecretCredential** parameter to **Connect-MgGraph**. See [Get-Credential](/powershell/module/microsoft.powershell.security/get-credential) on how to get or create credentials.
+
+```powershell
+$ClientSecretCredential = Get-Credential -Username "Client_Id"
+# Enter client_secret in the password prompt.
+Connect-MgGraph -TenantId "Tenant_Id" -ClientSecretCredential $ClientSecretCredential
+```
+
+#### Using managed identity
+
+A common challenge when writing automation scripts is the management of secrets, credentials, certificates, and keys used to secure communication between services. Eliminate the need to manage credentials by allowing the module to obtain access tokens for Azure resources that are protected by Azure AD. The identity is managed by the Azure platform and does not require you to provision or rotate any secrets.
+
+- System-assigned managed identity:
+
+    Uses an automatically managed identity on a service instance. The identity is tied to the lifecycle of a service instance.
+
+    ```powershell
+    Connect-MgGraph -Identity
+    ```
+
+- User-assigned managed identity:
+
+    Uses a user created managed identity as a standalone Azure resource.
+
+    ```powershell
+    Connect-MgGraph -Identity -ClientId "User_Assigned_Managed_identity_Client_Id"
+    ```
+
 ### Connecting to an environment or cloud
 
 By default, `Connect-MgGraph` targets the global public cloud. To target other clouds, see [Using Get-MgEnvironment](#using-get-mgenvironment).
@@ -196,34 +228,6 @@ User.Read
 User.ReadWrite.All
 ```
 
-## Using Get-MgProfile
-
-By default the Microsoft Graph PowerShell commands target the v1.0 API version. Commands for APIs that are only available in beta aren't available in PowerShell by default.
-
-To check your current profile, run:
-
-```powershell
-Get-MgProfile
-```
-
-```Output
-Name Description
----- -----------
-v1.0 A snapshot of the Microsoft Graph v1.0 API for the Global cloud.
-```
-
-## Using Select-MgProfile
-
-Use `Select-MgProfile` to change your target API version.
-
-To change to the beta version, run:
-
-```powershell
-Select-MgProfile -Name Beta
-```
-
-To switch back to using v1.0 API commands, specify **v1.0** for the name parameter.
-
 ## Using Invoke-MgGraphRequest
 
 `Invoke-MgGraphRequest` issues REST API requests to the Graph API. It works for any Graph API if you know the REST URI, method and optional body parameter. This command is especially useful for accessing APIs for which there isn't an equivalent cmdlet yet.

microsoftgraph/docs-conceptual/get-started.md

@@ -2,11 +2,11 @@
 title: "Get started with the Microsoft Graph PowerShell SDK"
 description: "Get started with the Microsoft Graph PowerShell SDK by using it perform some basic tasks."
 
-author: jasonjoh
+author: msewaweru
 manager: CelesteDG
 ms.topic: quickstart
-ms.date: 04/25/2023
-ms.author: jasonjoh
+ms.date: 05/17/2023
+ms.author: eunicewaweru
 ---
 
 # Get started with the Microsoft Graph PowerShell SDK
@@ -15,15 +15,11 @@ In this guide, you'll use the Microsoft Graph PowerShell SDK to perform some bas
 
 ## API version
 
-By default, the SDK uses the [Microsoft Graph REST API v1.0](/graph/api/overview?view=graph-rest-1.0&preserve-view=true). Cmdlets are available for the API version that is selected. You can change the profile by using the `Select-MgProfile` command.
-
-```powershell
-Select-MgProfile -Name "beta"
-```
+The SDK contains 2 modules, Microsoft.Graph and Microsoft.Graph.Beta, that call the [Microsoft Graph REST API v1.0](/graph/api/overview?view=graph-rest-1.0&preserve-view=true) and [Microsoft Graph REST API beta](/graph/api/overview?view=graph-rest-beta&preserve-view=true), respectively. Cmdlets are available for the module that is installed.
 
 ## Authentication
 
-The PowerShell SDK supports two types of authentication: delegated access, and app-only access. In this guide, you'll use delegated access to sign in as a user, grant consent to the SDK to act on your behalf, and call the Microsoft Graph.
+The PowerShell SDK supports two types of authentication: *delegated access*, and *app-only access*. In this guide, you'll use delegated access to sign in as a user, grant consent to the SDK to act on your behalf, and call the Microsoft Graph.
 
 For details on using app-only access for unattended scenarios, see [Use app-only authentication with the Microsoft Graph PowerShell SDK](app-only.md).
 
@@ -68,7 +64,7 @@ Use the `Connect-MgGraph` command to sign in with the required scopes. You'll ne
 Connect-MgGraph -Scopes "User.Read.All","Group.ReadWrite.All"
 ```
 
-The command prompts you to go to a web page to sign in using a device code. Once you've done that, the command indicates success with a `Welcome To Microsoft Graph!` message. You only need to sign in once per session.
+The command prompts you to go to a web page to sign in with your credentials. Once you've done that, the command indicates success with a `Welcome To Microsoft Graph!` message. You only need to sign in once per session.
 
 > [!TIP]
 > You can add additional permissions by repeating the `Connect-MgGraph` command with the new permission scopes.

microsoftgraph/docs-conceptual/navigating.md

@@ -2,11 +2,11 @@
 title: "Navigating the Microsoft Graph PowerShell SDK"
 description: "The Microsoft Graph PowerShell SDK contains a large number of commands. Learn how to find the right command for what you want to achieve."
 
-author: jasonjoh
+author: msewaweru
 manager: CelesteDG
 ms.topic: conceptual
-ms.date: 04/25/2023
-ms.author: jasonjoh
+ms.date: 05/17/2023
+ms.author: eunicewaweru
 ---
 
 # Navigating the Microsoft Graph PowerShell SDK
@@ -37,6 +37,9 @@ For functions and actions, it's a little more complicated. APIs in Microsoft Gra
 
 Let's look at some examples. The [getSchedule](/graph/api/calendar-getschedule?view=graph-rest-1.0&preserve-view=true) API uses `get`, and `Get` is an approved PowerShell verb, so its command is `Get-MgUserCalendarSchedule`. The [cancel](/graph/api/event-cancel?view=graph-rest-beta&preserve-view=true) API on an event on the other hand, uses a non-approved verb `cancel`. The approved verb for canceling or discontinuing something is `Stop`, so the command is `Stop-MgUserEvent`. Finally, the [snoozeReminder](/graph/api/event-snoozereminder?view=graph-rest-1.0&preserve-view=true) API's verb, `snooze`, has no PowerShell-approved equivalent. For APIs like that, the SDK uses the verb `Invoke`, so that API's command is `Invoke-MgSnoozeUserEventReminder`.
 
+> [!NOTE]
+> For Beta cmdlets add a **Beta** prefix before the resource. For example, the beta version of the Get-MgUser cmdlet is **Get-MgBetaUser**.
+
 ### Command nouns
 
 By now you may have noticed that all nouns in the SDK's commands start with `Mg`. This prefix helps to avoid naming conflicts with other PowerShell modules. With that in mind, it should make sense that a command like `Get-MgUser` is used to get a user. Following PowerShell convention, even though the noun is singular, those same commands can return multiple results if no specific instance is requested.