Merge branch 'main' into alvinashcraft/main-settings-uris-copilot-personalization

Author: alvinashcraft

.openpublishing.redirection.json

@@ -8274,6 +8274,11 @@
       "source_path": "uwp/devices-sensors/scan-from-your-app.md",
       "redirect_url": "/windows/apps/develop/devices-sensors/scan-from-your-app",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/dev-home/project-ironsides.md",
+      "redirect_url": "windows/dev-home/dev-diagnostics",
+      "redirect_document_id": false
     }
   ]
 }

hub/apps/develop/feeds/feed-provider-manifest.md

@@ -85,6 +85,8 @@ Represents the registration for a single feed.
 | **ContentUri** | string | Yes | The URI from which feed content is retrieved. | N/A |
 | **Icon** | string | Yes | The package-relative path to an icon image file that is displayed in the Widgets Board. | N/A |
 | **WebRequestFilter** | string | No | A web request filter string specifying the set of URLs for which the resource requests will be redirected to the feed provider's implementation of **IFeedResourceProvider**. The pattern is expressed using the format described in [Match Patterns](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Match_patterns). The filter string in the registration must use [Punycode](https://en.wikipedia.org/wiki/Punycode) where necessary. All content types will be redirected when matched so the filter should only resolve to content intended to be obtained through the **IFeedResourceProvider** in the application. | N/A |
+| **ExcludedRegions** | string | No | A list of regions where the feed should not be available. Feeds can specify **ExcludedRegions** or **ExclusiveRegions** but must not specify both in a single feed definition. The value of the attribute is a comma separated list of two character region codes.| N/A |
+| **ExclusiveRegions** | string | No | A list of the only regions where the feed should be available. Feeds can specify **ExcludedRegions** or **ExclusiveRegions** but must not specify both in single feed definition. The value of the attribute is a comma separated list of two character region codes.| N/A |
 
 
 You can use localized resources instead of string literals for the UI-facing attribute values. For more information, see [Localize strings in your UI and app package manifest](/windows/uwp/app-resources/localize-strings-ui-manifest).
@@ -101,10 +103,13 @@ The following code example illustrates the usage of the feed package manifest XM
               <CreateInstance ClassId="ECB883FD-3755-4E1C-BECA-D3397A3FF15C" />
           </Activation>
           <Definitions>
-              <Definition Id="Contoso_Feed" DisplayName="ms-resource:FeedDisplayName"                  Description="ms-resource:FeedDescription"
+              <Definition Id="Contoso_Feed" 
+                  DisplayName="ms-resource:FeedDisplayName"                  
+                  Description="ms-resource:FeedDescription"
                   ContentUri="https://contoso.com/news"
                   Icon="ms-appx:Images\ContosoFeedIcon.png"
-                  WebRequestFilter="https://contoso.com/*/feed/appResource/*" >
+                  WebRequestFilter="https://contoso.com/*/feed/appResource/*"
+                  ExcludedRegions="FR,DE,IT">
               </Definition>
           </Definitions>
       </FeedProvider>

hub/apps/develop/widgets/widget-provider-manifest.md

@@ -122,6 +122,9 @@ Represents the registration for a single widget.
 | **Description** | string | Yes | Short description of the widget. | N/A |
 | **AllowMultiple** | boolean | No | Set to false if only one instance of this widget is supported. This attribute is optional and the default value is true. | true |
 | **IsCustomizable** | boolean | No | Introduced in Windows App SDK 1.4. Set to true if your app supports widget customization. This causes the **Customize widget** button to be displayed in the widget's ellipsis menu. | false |
+| **AdditionalInfoUri** | string | No | A URI that can be associated with the widget to be used when the user clicks on the title bar of the widget frame or when clicking the **Powered by** element of its context menu.|  N/A |
+| **ExcludedRegions** | string | No | A list of regions where the widget should not be available. Widgets can specify **ExcludedRegions** or **ExclusiveRegions** but must not specify both in a single widget definition. The value of the attribute is a comma separated list of two character region codes.| N/A |
+| **ExclusiveRegions** | string | No | A list of the only regions where the widget should be available. Widgets can specify **ExcludedRegions** or **ExclusiveRegions** but must not specify both in single widget definition. The value of the attribute is a comma separated list of two character region codes.| N/A |
 
 ## Capabilities
 
@@ -200,6 +203,8 @@ The following code example illustrates the usage of the widget package manifest
             Id="Weather_Widget"
             DisplayName="Microsoft Weather Widget"
             Description="Weather Widget Description"
+            AdditionalInfoUri="https://contoso.com/widgets/Weather"
+            ExclusiveRegions="US,UK"
             AllowMultiple="true">
             <Capabilities>
               <Capability>

hub/apps/publish/organizational-licensing.md

@@ -54,7 +54,7 @@ Offline licensing allows organizations to acquire your app on a volume basis, an
 Currently, developer accounts located in certain markets are able to offer paid apps for volume acquisition through Microsoft Store for Business. 
 
 > [!NOTE]
-> In some markets, the price shown for an app in Microsoft Store for Business or Microsoft Store for Education may be different than the price shown to retail customers in the Microsoft Store for the same price tier. Payout of proceeds from organizational purchases works just the same as it does for consumer purchases of your app. For more info, see [Getting paid](/partner-center/marketplace-get-paid) and the [App Developer Agreement](/legal/windows/agreements/app-developer-agreement). For a list of markets where Microsoft Store for Business and Microsoft Store for Education are available, see [Microsoft Store for Business and Microsoft Store for Education overview](/windows/manage/windows-store-for-business-overview#supported-markets).
+> In some markets, the price shown for an app in Microsoft Store for Business or Microsoft Store for Education may be different than the price shown to retail customers in the Microsoft Store for the same price tier. Payout of proceeds from organizational purchases works just the same as it does for consumer purchases of your app. For more info, see [Getting paid](/partner-center/marketplace-get-paid) and the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905). For a list of markets where Microsoft Store for Business and Microsoft Store for Education are available, see [Microsoft Store for Business and Microsoft Store for Education overview](/windows/manage/windows-store-for-business-overview#supported-markets).
 
 If your country or region is not listed below, your paid apps currently will not be offered in Microsoft Store for Business and Microsoft Store for Education. If this is the case, the organizational licensing selections you make for your paid apps may be applied at a later time, as we may add support for submissions from additional developer account markets in the future.
 

hub/apps/publish/partner-center/open-a-developer-account.md

@@ -40,14 +40,14 @@ For more details, you can refer to the steps below:
 1. Enter the **publisher display name** that you want to use (50 characters or fewer). Select this carefully, as customers will see this name when browsing and will come to know your apps by this name. 
 
    > [!NOTE]
-   > Make sure you have the rights to use the name you enter here. If someone else has trademarked or copyrighted the name you picked, your account could be closed. See [app developer agreement](/legal/windows/agreements/app-developer-agreement) for more info. If someone else is using a publisher display name for which you hold the trademark or other legal right, [contact Microsoft](https://www.microsoft.com/info/cpyrtInfrg.html).
+   > Make sure you have the rights to use the name you enter here. If someone else has trademarked or copyrighted the name you picked, your account could be closed. See [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) for more info. If someone else is using a publisher display name for which you hold the trademark or other legal right, [contact Microsoft](https://www.microsoft.com/info/cpyrtInfrg.html).
 
 1. Enter the **contact info** you want to use for your developer account.
 
    > [!NOTE]
    > We'll use this info to contact you about account-related matters. For example, you'll receive an email confirmation after you complete your registration. After that, we'll send messages when we pay you or if you need to fix something with your account. We may also send informational emails as described earlier, unless you opt out of receiving non-transactional emails.
    
-1. Then, read and accept the terms and conditions of the [app developer agreement](/legal/windows/agreements/app-developer-agreement). 
+1. Then, read and accept the terms and conditions of the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905). 
 
 1. Select **Accept and Continue** to move on to the **Payment** section.
 
@@ -96,11 +96,11 @@ For more details, you can refer to the steps below:
 1. Enter the **publisher display name** that you want to use (50 characters or fewer). Select this carefully, as customers will see this name when browsing and will come to know your apps by this name. Be sure to use your organization's registered business name or trade name. If you enter a name that someone else has already selected, or if someone else has the rights to use that name, we won't permit you to use it.
 
    > [!NOTE]
-   > Make sure you have the rights to use the name you enter here. If someone else has trademarked or copyrighted the name you picked, your account could be closed. See [app developer agreement](/legal/windows/agreements/app-developer-agreement) for more info. If someone else is using a publisher display name for which you hold the trademark or other legal right, [contact Microsoft](https://www.microsoft.com/info/cpyrtInfrg.html).
+   > Make sure you have the rights to use the name you enter here. If someone else has trademarked or copyrighted the name you picked, your account could be closed. See [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) for more info. If someone else is using a publisher display name for which you hold the trademark or other legal right, [contact Microsoft](https://www.microsoft.com/info/cpyrtInfrg.html).
 
 1. Upload **a legal document** with your company address and name details such as formation documents, government issued letter/license etc.   
 
-1. Then, read and accept the terms and conditions of the [app developer agreement](/legal/windows/agreements/app-developer-agreement). 
+1. Then, read and accept the terms and conditions of the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905). 
 
 1. Select **Accept and Continue** to move on to the **Payment** section.
 

hub/apps/publish/publish-your-app/add-on/market-selection.md

@@ -401,7 +401,7 @@ You can choose to list your app (or add-on) in one or more of the following mark
 
 ## Price considerations for specific markets
 
-Payment methods such as gift cards and mobile operator billing can help increase sales of paid apps and in-app purchase items. Due to the higher costs to enable such payment methods, a Commerce Expansion Adjustment is added to the Store Fee deducted from Net Receipts to calculate the App Proceeds payable for paid apps and in-app purchase transactions in the countries/regions and using the payment methods in the tables below. You may want to consider if the Commerce Expansion Adjustment applies in a country/region where your app is available and factor that into your market pricing strategy. Details about the Commerce Expansion Adjustment can be found in the [App Developer Agreement](/legal/windows/agreements/app-developer-agreement).
+Payment methods such as gift cards and mobile operator billing can help increase sales of paid apps and in-app purchase items. Due to the higher costs to enable such payment methods, a Commerce Expansion Adjustment is added to the Store Fee deducted from Net Receipts to calculate the App Proceeds payable for paid apps and in-app purchase transactions in the countries/regions and using the payment methods in the tables below. You may want to consider if the Commerce Expansion Adjustment applies in a country/region where your app is available and factor that into your market pricing strategy. Details about the Commerce Expansion Adjustment can be found in the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905).
 
 The Commerce Expansion Adjustment will be applied to all transactions processed for the specified Country/Region and Payment Methods as of the Effective Date. This information will be updated monthly; new countries/regions and payment methods will be listed within thirty (30) days after the Commerce Expansion Adjustment takes effect for that country/region and payment method.
 

hub/apps/publish/publish-your-app/add-on/product-declarations.md

@@ -16,7 +16,7 @@ The following sections describe some of the declarations and what you need to co
 
 1. If your app is using Microsoft Commerce, do not tick this box.
 2. If your app does not use Microsoft Commerce, tick this box.
-3. Per the [App Developer Agreement](/legal/windows/agreements/app-developer-agreement), apps that were created and submitted prior to June 29, 2015, could continue to offer in-app purchasing functionality without using Microsoft's commerce engine, so long as the purchase functionality complies with the [Microsoft Store Policies](../../store-policies.md#108-financial-transactions). If this applies to your app, you must check this box.
+3. Per the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905), apps that were created and submitted prior to June 29, 2015, could continue to offer in-app purchasing functionality without using Microsoft's commerce engine, so long as the purchase functionality complies with the [Microsoft Store Policies](../../store-policies.md#108-financial-transactions). If this applies to your app, you must check this box.
 
 ## This app has been tested to meet accessibility guidelines
 

hub/apps/publish/publish-your-app/add-on/resolve-submission-errors.md

@@ -47,7 +47,7 @@ Review this list to help avoid issues that frequently prevent apps from getting
 
 - [Provide any necessary info](./manage-submission-options.md#notes-for-certification) required to use your app, such as the user name and password for a test account if your app requires users to log in to a service, or any steps required to access hidden or locked features.
 
-- Include a [privacy policy URL](./support-info.md#privacy-policy-url) if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](/legal/windows/agreements/app-developer-agreement) and the [Microsoft Store Policies](../../store-policies.md).
+- Include a [privacy policy URL](./support-info.md#privacy-policy-url) if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and the [Microsoft Store Policies](../../store-policies.md).
 
 - Make sure that your app's description clearly represents what your app does. For help, see our guidance on [writing a great app description](./write-great-app-description.md).
 

hub/apps/publish/publish-your-app/add-on/support-info.md

@@ -19,7 +19,7 @@ In this section, you must indicate whether or not your app accesses, collects, o
 > [!NOTE]
 > If we detect that your packages declare [capabilities](/windows/uwp/packaging/app-capability-declarations) that could allow personal information to be accessed, transmitted, or collected, we will mark this question as **Yes**, and you will be required to enter a privacy policy URL.
 
-To help you determine if your app requires a privacy policy, review the [App Developer Agreement](/legal/windows/agreements/app-developer-agreement) and the [Microsoft Store Policies](../../store-policies.md#105-personal-information).
+To help you determine if your app requires a privacy policy, review the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and the [Microsoft Store Policies](../../store-policies.md#105-personal-information).
 
 > [!NOTE]
 > Microsoft doesn't provide a default privacy policy for your app. Likewise, your app is not covered by any Microsoft privacy policy.

hub/apps/publish/publish-your-app/msi/app-certification-process.md

@@ -62,7 +62,7 @@ It is highly recommended that your EXE/MSI app and the Portable Executable (PE)
 
 ### Privacy policy
 
-Include a valid privacy policy URL if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](/legal/windows/agreements/app-developer-agreement) and the [Microsoft Store Policies](../../store-policies.md#105-personal-information).
+Include a valid privacy policy URL if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and the [Microsoft Store Policies](../../store-policies.md#105-personal-information).
 
 ### Additional tests
 
@@ -78,7 +78,7 @@ Review this list to help avoid issues that frequently prevent apps from getting
 - Ensure that your app does not crash without network connectivity. Even if a connection is required to use your app, it needs to perform appropriately when no connection is present.
 - Provide any necessary info required to use your app, such as the username and password for a test account if your app requires users to log in to a service, or any steps required to access hidden or locked features.
 - Configure your app's installer to provide your app’s information such as ProductName, Publisher Name, Default Language, Version info (as applicable) in places where customers expect to find such information such as ‘Add/Remove Programs’ in Windows. This information is part of your app’s installer package. See [setting installer properties](/windows/win32/msi/property-reference#product-information-properties) for more details on how to set properties for your Windows installer
-- Include a privacy policy URL if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](/legal/windows/agreements/app-developer-agreement) and the [Microsoft Store Policies](../../store-policies.md#105-personal-information).
+- Include a privacy policy URL if your app requires one; for example, if your app accesses any kind of personal information in any way or is otherwise required by law. To help determine if your app requires a privacy policy, review the [App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and the [Microsoft Store Policies](../../store-policies.md#105-personal-information).
 - Make sure that your app's description clearly represents what it does. For help, see our guidance on [writing a great app description](./write-great-app-description.md).
 - Do not declare your app as accessible unless you have specifically engineered and tested it for accessibility scenarios.
 - Review the [Microsoft Store Policies](../../store-policies.md) to ensure your app meets all the requirements listed there.