Merge pull request MicrosoftDocs#278 from MicrosoftDocs/master

Master to Live push for Certification Updates

Author: bezhan-msft

powerquery-docs/CertificationSubmission.md

@@ -0,0 +1,58 @@
+---
+title: Power Query connector certification submission
+description: Instructions for submitting a Power Query custom connector for certification.
+author: bezhan-msft
+ms.service: powerquery
+ms.topic: conceptual
+ms.date: 03/01/2020
+ms.author: bezhan
+
+LocalizationGroup: reference
+---
+
+# Power Query connector submission
+
+## Introduction
+
+This article provides instructions for how to submit your Power Query custom connector for certification. Do not submit your connector for certification unless you've been directed to by your Microsoft contact.
+
+## Prerequisites
+
+After you've been approved for certification, ensure that your connector meets the [certification requirements](https://docs.microsoft.com/power-query/connectorcertification#certification-requirements) and follows all feature, style, and security guidelines. Prepare the [submission artifacts](https://docs.microsoft.com/power-query/connectorcertification#certification-requirements) for submission.
+
+## Submitting to the Connector Certification Portal
+
+The Connector Certification Portal is an experience within [ISV Studio](https://aka.ms/ISVStudio) that allows Microsoft partners and ISVs to submit, view, and manage connectors submitted for certification. After submission, communication between Microsoft and the partner connector developer will be through the Connector Certification Portal.
+
+### Initial Submission
+
+1. Navigate to [ISV Studio](https://aka.ms/ISVStudio) and log in with your work Microsoft account. Personal accounts aren't supported in this experience.
+
+2. Select the **Connector certification** tab on the left to launch the Connector Certification Portal experience.
+
+3. Select **Power Query** as your connector type.
+
+4. Read and agree to our connector Partner Agreement. If there is a separate agreement governing the relationship between your organization and Microsoft, let your Microsoft contact know.
+
+5. Upload your `.mez` file and complete the form with information on your connector. Submit the form to finish the connector submission process. Once submitted, you can use the Activity Control experience on the right to communicate with your Microsoft contact. 
+
+6. Read the guidelines for providing [documentation](https://docs.microsoft.com/power-query/providing-user-documentation) for your custom connector. Submit a pull request to our public [documentation repository](https://github.com/MicrosoftDocs/powerquery-docs/tree/master/powerquery-docs/Connectors) with an `.md` file following the custom connector documentation guidelines. This step is crucial to ensure users know how to use your connector. Once the pull request has been made, send a link to the pull request in the Activity Control experience in the Connector Certification Portal. 
+
+7. If you would like to add teammates to manage your connector, let your Microsoft contact know.
+
+### Updates
+
+Updates to your connector submission can be made at any time, except when your connector is in the process of production deployment. When you are submitting an update, ensure that you submit an update to your existing submission, rather than creating a new submission.
+
+1. Navigate to the **Connector certification** experience within [ISV Studio](https://aka.ms/ISVStudio).
+
+2. From the list of connectors you manage, select the connector submission to view its connector versions.
+
+3. Select the most recent connector version.
+
+4. At the bottom left, select the "Submit an update" button. 
+
+5. You can upload a new version of artifacts and complete the submission form again.
+
+6. After submitting the connector form, within the Activity Control chat feature on the right, submit a short changelog explaining the connector update. This information should be public and written in a customer-facing way, as it will be included in the next Power BI Desktop blog update. 
+

powerquery-docs/ConnectorCertification.md

@@ -81,7 +81,7 @@ We have a certain set of requirements for certification. We recognize that not e
 Please ensure the connector files that you submit include all of the following:
 
 * Connector (.mez) file
-  * The .mez file should follow style standards.
+  * The .mez file should follow style standards and be named similarly to the product or service name. It should not include words like "Power BI", "Connector" or "API". 
   * Name the .mez file: ```ProductName.mez```
 
 * Power BI Desktop (.pbix) file for testing
@@ -108,14 +108,14 @@ The connector must follow a set of feature and style rules to meet a usability s
    * Have [version adornment](HandlingVersioning.md) on section.
    * Provide [function documentation metadata](HandlingDocumentation.md).
    * Have [TestConnection handler](HandlingGatewaySupport.md).
-   * Follow naming conventions (for example, `DataSourceKind.FunctionName`).
+   * Follow naming conventions (for example, `DataSourceKind.FunctionName`). It should not include words like "Power BI", "Connector" or "API". 
 
 * The ```FunctionName``` should make sense for the domain (for example "Contents", "Tables", "Document", "Databases", and so on).
 
 * The connector SHOULD:
    * Have icons.
    * Provide a navigation table.
-   * Place strings in a `resources.resx` file.
+   * Place strings in a `resources.resx` file. URLs and values should be hardcoded in the connector code and not be placed in the `resources.resx` file. 
 
 ### Security
 

powerquery-docs/Connectors/Web/Web.md

@@ -63,6 +63,10 @@ To load data from a web site with Power Query Desktop:
 
    * **Organizational account**: Select this authentication method if the web page requires organizational account credentials.
 
+
+   >[!Note]
+   >When uploading the report to the Power BI service, only the **anonymous**, **Windows** and **basic** authentication methods are available.
+
    The level you select for the authentication method determines what part of a URL will have the authentication method applied to it. If you select the top-level web address, the authentication method you select here will be used for that URL address or any subaddress within that address. However, you might not want to set the top URL address to a specific authentication method because different subaddresses could require different authentication methods. For example, if you were accessing two separate folders of a single SharePoint site and wanted to use different Microsoft Accounts to access each one.
 
    Once you've set the authentication method for a specific web site address, you won't need to select the authentication method for that URL address or any subaddress again. For example, if you select the https://en.wikipedia.org/ address in this dialog, any web page that begins with this address won't require that you select the authentication method again.  

powerquery-docs/TOC.yml

@@ -457,10 +457,14 @@
           href: HandlingGatewaySupport.md
         - name: "Handling connector signing"
           href: HandlingConnectorSigning.md
-      - name: Certification
-        href: ConnectorCertification.md
-      - name: "Custom connector documentation"
-        href: providing-user-documentation.md
+      - name: Connector Certification
+        items:
+        - name: Overview
+          href: ConnectorCertification.md
+        - name: Submission
+          href: CertificationSubmission.md
+        - name: "Custom connector documentation"
+          href: providing-user-documentation.md
     - name: Resources
       items:
       - name: "Power BI documentation"