Added Blazor sample page

Author: JimDaly

powerapps-docs/developer/data-platform/TOC.yml

@@ -438,6 +438,8 @@
     href: discovery-service.md
   - name: "Sample: Global Discovery Service"
     href: sample-global-discovery-service-csharp.md
+  - name: "Sample: Blazor WebAssembly with Global Discovery"
+    href: sample-blazor-web-assembly-global-discovery.md
   - name: Tutorials 
     items:
     - name: "Tutorial: Register an app with Azure Active Directory"

powerapps-docs/developer/data-platform/discovery-service.md

@@ -1,7 +1,7 @@
 ---
 title: "Discover user organizations (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Your client application may connect to multiple Dataverse environments. Use the Global Discovery Service to find which environments the user of your application can access."
-ms.date: 07/01/2022
+ms.date: 07/18/2022
 ms.reviewer: pehecke
 ms.topic: article
 author: ImadYanni # GitHub ID
@@ -122,12 +122,12 @@ The following table describes the properties of the `Instance` Entity from the $
 |`Id`|Guid|The OrganizationId for the environment.|
 |`IsUserSysAdmin`|Boolean|Whether the calling user has the system administrator role for the environment.|
 |`LastUpdated`|DateTimeOffset|When the environment was last updated. |
-|`OrganizationType`|Int32|The type of the organization. Values correspond to the OrganizationType Enum|
+|`OrganizationType`|Int32|The type of the organization. Values correspond to the <xref:Microsoft.Dynamics.CRM.OrganizationType?text=OrganizationType EnumType>|
 |`Purpose`|String|Information for the purpose provided when the environment was created.|
 |`Region`|String|A 2-3 letter code for region where the environment is located. |
 |`SchemaType`|String|For internal use only.|
-|`State`|Int32|Whether the organization is enabled (`0`) or eisabled (`1`).|
-|`StatusMessage`|Int32|TODO: This is an integer value. What does it mean?|
+|`State`|Int32|Whether the organization is `0`:enabled  or `1`:disabled.|
+|`StatusMessage`|Int32|One of the following values: <br /> `0`:`InstanceLocked`<br /> `1`:`PendingServiceInstanceMove`<br /> `2`:`InstanceFailed`<br /> `3`:`Provisioning` <br /> `4`:`InActiveOrganizationStatus`<br /> `5`:`NewInstance`<br /> `6`:`InstancePickerReady`   |
 |`TenantId`|Guid|The Id of the tenant associated to the instance|
 |`TrialExpirationDate`|DateTimeOffset|The date when the trial period for the instance expires.|
 |`UniqueName`|String|The Unique Name for the instance.|
@@ -163,7 +163,7 @@ odata-version: 4.0
 }
 ```
 
-Use the `FriendlyName` property for your application UI so the user will recognize the name of the environment. Use the `ApiUrl` to connect to the Dataverse Web API.
+Use the `FriendlyName` property for your application UI so the user will recognize the name of the environment. Use the `ApiUrl` to connect to Dataverse.
 
 The rest of the properties are primarily for filtering.
 
@@ -235,8 +235,6 @@ You can use the following string query functions:
 
 For .NET applications you can use <xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient?text=Dataverse.Client.ServiceClient>.<xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient.DiscoverOnlineOrganizationsAsync%2A?text=DiscoverOnlineOrganizationsAsync Method> to call the Global Discovery Services.
 
-TODO: Ask Matt B to comment on the key benefits provided by this method.
-
 ```csharp
  // Set up user credentials
 var creds = new System.ServiceModel.Description.ClientCredentials();
@@ -256,7 +254,7 @@ DiscoverOrganizationsResult organizationsResult = await ServiceClient.DiscoverOn
 return organizationsResult;
 ```
 
-While the `DiscoverOnlineOrganizationsAsync` method uses the same OData endpoint and enables that it be passed in the `discoveryServiceUri` parameter, it does not return data in the shape of an *Instance*. Data is returned as an <xref:Microsoft.PowerPlatform.Dataverse.Client.Model.DiscoverOrganizationsResult?text=DiscoverOrganizationsResult Class> that includes a <xref:Microsoft.PowerPlatform.Dataverse.Client.Model.DiscoverOrganizationsResult.OrganizationDetailCollection?text=OrganizationDetailCollection Property> which contains a collection of <xref:Microsoft.Xrm.Sdk.Discovery.OrganizationDetail?text=OrganizationDetail Class> instances. This class contains the same information as the Instance types returned by the OData service.
+While the `DiscoverOnlineOrganizationsAsync` method uses the same OData endpoint and enables that it be passed in the `discoveryServiceUri` parameter, it does not return data in the shape of an *Instance*. Data is returned as an <xref:Microsoft.PowerPlatform.Dataverse.Client.Model.DiscoverOrganizationsResult?text=DiscoverOrganizationsResult Class> that includes a <xref:Microsoft.PowerPlatform.Dataverse.Client.Model.DiscoverOrganizationsResult.OrganizationDetailCollection?text=OrganizationDetailCollection Property> which contains a collection of <xref:Microsoft.Xrm.Sdk.Discovery.OrganizationDetail?text=OrganizationDetail Class> instances. This class contains the same information as the `Instance` types returned by the OData service.
 
 > [!NOTE]
 > While the `DiscoverOnlineOrganizationsAsync.discoveryServiceUri` parameter accepts a URL to the Global Discovery Service, any `$select` or `$filter` query options used will be ignored. The `DiscoverOnlineOrganizationsAsync.discoveryServiceUri` parameter is optional and if not provided will default to the Commercial cloud.
@@ -286,14 +284,13 @@ For .NET Full Framework applications you can continue to use the <xref:Microsoft
   return organizations.ToList();
 ```
 
-Like the `ServiceClient.DiscoverOnlineOrganizationsAsync` method, the `CrmServiceClient.DiscoverGlobalOrganizations` method also does not return data as an *Instance*. It returns a
-
-<xref:Microsoft.Xrm.Sdk.Discovery.OrganizationDetailCollection?text=OrganizationDetailCollection> which contains a collection of <xref:Microsoft.Xrm.Sdk.Discovery.OrganizationDetail?text=OrganizationDetail Class> instances that contains the same information as the Instance types returned by the OData service.
+Like the `ServiceClient.DiscoverOnlineOrganizationsAsync` method, the `CrmServiceClient.DiscoverGlobalOrganizations` method also does not return data as an *Instance*. It returns a <xref:Microsoft.Xrm.Sdk.Discovery.OrganizationDetailCollection?text=OrganizationDetailCollection> which contains a collection of <xref:Microsoft.Xrm.Sdk.Discovery.OrganizationDetail?text=OrganizationDetail Class> instances that contains the same information as the `Instance` types returned by the OData service.
 
 ### See Also
 
 [Sample: Global Discovery Service Sample (C#)](sample-global-discovery-service-csharp.md)<br />
-[Sample: Access the Discovery service using CrmServiceClient](org-service/samples/access-discovery-service.md)
+[Sample: Access the Discovery service using CrmServiceClient](org-service/samples/access-discovery-service.md)<br />
+[Sample: Blazor WebAssembly with Global Discovery](sample-blazor-web-assembly-global-discovery.md)
 
 
 [!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/sample-blazor-web-assembly-global-discovery.md

@@ -0,0 +1,105 @@
+---
+title: "Sample: Blazor WebAssembly with Global Discovery (C#) (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "This sample a Blazor WebAssembly project that uses the Global Discovery Service and Dataverse Web API to access multiple environments available to the user." # 115-145 characters including spaces. This abstract displays in the search result.
+ms.date: 07/18/2022
+author: ImadYanni
+ms.author: iyanni
+ms.reviewer: jdaly
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+contributors: 
+  - JimDaly
+  - phecke
+---
+# Sample: Blazor WebAssembly with Global Discovery
+
+This sample shows how to use the Global Discovery service from a Blazor WebAssembly application.
+
+You can download the sample from [https://github.com/microsoft/PowerApps-Samples/tree/master/cds/webapi/C#/BlazorCDS](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/webapi/C%23/BlazorCDS)
+
+This sample is a modification of the steps in the [Tutorial: Create an ASP.NET Core Blazor WebAssembly app using Microsoft Dataverse](walkthrough-blazor-webassembly-single-tenant.md)
+
+## How to run this sample
+
+1. Download or clone the [Samples](https://github.com/microsoft/PowerApps-Samples) repo so that you have a local copy.
+1. Follow the instructions in [Setup](#setup) to create an Azure Active Directory app registration and run the sample.
+
+## What this sample does
+
+This sample demonstrates how to provide a select (drop-down) control in a web application to allow users to switch environments that they have access to.
+
+## How this sample works
+
+The `Pages/EnvironmentChooser.razor `file provides the UI to allow users to select from available environments based on their credentials after they have logged in.
+
+This page depends on a named definition of an HttpClient (`GDSClient`) in  Program.cs that is configured to access the Global Discovery Service. Access to the Global Discovery Service is added to the available scopes when the user logs in. When the user selects a different environment, the `SelectedEnvUrl` in `Models/AppState.cs` changes.
+
+Access to the account records is provided by `Pages/FetchAccounts.razor` with an access token that depends on the selected environment.
+
+### Setup
+
+To run this sample you must first configure an Azure Active Directory application on your tenant and update the `BlazorCDS\wwwroot\appsettings.json` file to replace the placeholder `ClientId` value with the application (client) Id. Use the following steps:
+
+#### Create an app registration
+
+1. Go to [Azure](https://portal.azure.com/).
+1. Select **Azure Active Directory**.
+1. Go To **App registrations**.
+1. Select **New Registration**.
+1. Enter the following:
+
+  |Field|Value|
+  |---------|---------|
+  |Name|Your choice. You might use: `BlazorGlobalDiscoverySample`|
+  |Supported account types:|Accounts in this organization directory only (Single Tenant)|
+  |Redirect URI (optional)|`https://localhost:44363/authentication/login-callback`|
+
+1. Click **Register**.
+1. Copy the **Application (client) ID** value. You will need this when you [Update the project](#update-the-project).
+
+#### Configure Authentication
+
+1. Go to **Authentication**.
+1. Under **Implicit grant and hybrid flows**, select both of the following options:
+
+  - Access tokens (used for implicit flows)
+  - ID tokens (used for implicit and hybrid flows)
+
+1. Click **Save**.
+
+#### Configure Permissions
+
+1. Go to **API permissions**.
+1. Click **Add a permission**.
+1. In the **Request API permissions** fly-out, under the**Microsoft APIs** tab, select **Dynamics CRM**.
+1. Under **Select permissions**, select **user_impersonation**.
+1. Click **Add permissions**.
+1. Under **Configured permissions**, click **Grant admin consent** for {Your tenant name.}
+1. In the **Grant admin consent** confirmation dialog, click **Yes**.
+
+#### Update the project
+
+1. Open the BlazorCDS Visual Studio solution file (BlazorCDS.sln) with Visual Studio
+1. In **Solution Explorer**, expand `wwwroot` and open the `appsettings.json` file.
+1. Replace the placeholder `ClientId` value (`11111111-1111-1111-1111-111111111111`) with the application (client) ID value you copied in [Create an app registration](#create-an-app-registration).
+
+#### Run the sample
+
+In Visual Studio, click **IIS Express** to run the sample.
+
+### Demonstrate
+
+1. In the browser window that opens with the app, click **Log in**.
+1. Enter your credentials and you will see a select control with the label: **Choose an Environment**. The select control should list all the environments you have access to with the credentials you provided.
+1. Click **Fetch Accounts**. This should display a list of account records you have access to view in the selected environment.
+1. If you have more than one environment to choose from, select a different environment and the list of account records will be refreshed to represent the records available in that environment.
+
+### Clean up
+
+This sample makes no changes to data in your environment.
+
+
+[!INCLUDE [footer-banner](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/sample-global-discovery-service-csharp.md

@@ -1,7 +1,7 @@
 ---
 title: "Global Discovery Service Sample (C#) (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This sample shows how to access the global Discovery Service using the OData V4 RESTful API and the Dataverse.Client.ServiceClient" # 115-145 characters including spaces. This abstract displays in the search result.
-ms.date: 07/01/2022
+ms.date: 07/18/2022
 author: ImadYanni
 ms.author: iyanni
 ms.reviewer: jdaly
@@ -17,7 +17,10 @@ contributors:
 
 # Sample: Global Discovery Service (C#)
 
-This Visual Studio solution contains two projects that demonstrate how to use the Global Discovery Service.
+This Visual Studio solution contains two .NET 6.0 projects that demonstrate how to use the Global Discovery Service.
+
+- `REST` project shows using the OData endpoint
+- `ServiceClient` project shows using <xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient.DiscoverOnlineOrganizationsAsync%2A?text=Dataverse.Client.ServiceClient.DiscoverOnlineOrganizationsAsync Method>
 
 ## How to run this sample
 
@@ -41,23 +44,23 @@ To run the sample:
 
 Both the `REST` and `ServiceClient` samples do the same things:
 
-1. Retrieve the list of environments available for your credentials
-1. List the environments so you can select one
-1. Execute a WhoAmI message to return the SystemUser.UserId value for your account in the selected environment
+1. Retrieve the list of environments available for your credentials.
+1. List the environments so you can select one.
+1. Execute a `WhoAmI` message to return the `SystemUser.UserId` value for your account in the selected environment.
 
 ## How this sample works
 
 ### REST
 
-The REST project uses the MSAL libraries with an HttpClient to use the Global Discovery OData endpoint without the use of any additional assemblies.
+The `REST` project uses the MSAL libraries with an [HttpClient](/dotnet/api/system.net.http.httpclient) to use the Global Discovery OData endpoint without the use of any additional assemblies.
 
 ### ServiceClient
 
-The ServiceClient project uses the <xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient?text=Dataverse.Client.ServiceClient>.<xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient.DiscoverOnlineOrganizationsAsync%2A?text=DiscoverOnlineOrganizationsAsync Method> to use the Global Discovery OData endpoint.
+The `ServiceClient` project uses the <xref:Microsoft.PowerPlatform.Dataverse.Client.ServiceClient.DiscoverOnlineOrganizationsAsync%2A?text=Dataverse.Client.ServiceClient.DiscoverOnlineOrganizationsAsync Method> to use the Global Discovery OData endpoint.
 
 ### Demonstrates
 
-Both samples use the same Cloud enum defined in Cloud.cs to represent the different clouds that may be used with the Global Discovery Service.
+Both projects use the same `Cloud` enum defined in Cloud.cs to represent the different clouds that may be used with the Global Discovery Service.
 
 ```csharp
 using System.ComponentModel;
@@ -119,7 +122,7 @@ namespace PowerApps.Samples
 }
 ```
 
-The Program.cs file contains the following:
+The `REST` Program.cs file contains the following:
 
 ```csharp
 using Microsoft.Identity.Client;
@@ -369,7 +372,7 @@ namespace PowerApps.Samples
 
 #### ServiceClient Project
 
-The ServiceClient Project Program.cs file contains the following:
+The `ServiceClient` project Program.cs file contains the following:
 
 ```csharp
 using Microsoft.Crm.Sdk.Messages;
@@ -551,6 +554,7 @@ namespace PowerApps.Samples
 
 ## See Also
 
-[Discover user organizations](discovery-service.md)
+[Discover user organizations](discovery-service.md)<br />
+[Blazor web assembly sample](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/webapi/C%23/BlazorCDS)
 
 [!INCLUDE [footer-banner](../../includes/footer-banner.md)]