text:
Update push task docs

This PR updates the push task docs, to include a detailed explanation of a few properties ie: FileContent profile, Import mode, and dry run.

Learn Build status updates of commit b727e28:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

articles/azure-app-configuration/push-kv-devops-pipeline.md
:bulb:Suggestion

Details

articles/azure-app-configuration/push-kv-devops-pipeline.md

Line 77, Column 54: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/concept-config-file' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 8786a56:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

articles/azure-app-configuration/push-kv-devops-pipeline.md
:bulb:Suggestion

Details

articles/azure-app-configuration/push-kv-devops-pipeline.md

Line 77, Column 54: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/concept-config-file' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 2f74898:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

articles/azure-app-configuration/push-kv-devops-pipeline.md
:bulb:Suggestion

Details

articles/azure-app-configuration/push-kv-devops-pipeline.md

Line 77, Column 54: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/concept-config-file' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit ee210d5:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

articles/azure-app-configuration/push-kv-devops-pipeline.md
:bulb:Suggestion

Details

articles/azure-app-configuration/push-kv-devops-pipeline.md

Line 77, Column 54: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/concept-config-file' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@MaryanneNjeri, do we have an updated UI screenshot?

@MaryanneNjeri, do we have an updated UI screenshot?
BTW, the change will be more than a few lines. You may like to use the private repo. We will also get a nice preview of the doc.

Yes we do have an updated screenshot, let me send a new PR, through a private repo.

Dihantar daripada telefon saya-------- Mesej asal --------Daripada: MaryanneNjeri @.>Tarikh: Isn, 21 Nov 2022, 9:38 PTGKepada: MicrosoftDocs/azure-docs @.>Sk: Faizul mansor @.>, Manual @.>Tajuk: Re: [MicrosoftDocs/azure-docs] Update push task docs (PR #101601)
@MaryanneNjeri commented on this pull request.
In articles/azure-app-configuration/push-kv-devops-pipeline.md:

@@ -74,14 +74,25 @@ The following parameters are used by the App Configuration Push task:
"TestApp:Settings:Message": "Message data"
}
```
+- File Content Profile: The Configuration File's content profile. Default value is Default.

- **Default**: Refers to the conventional configuration file schema widely adopted.

- **Kvset**: Refers to a [file schema](https://github.com/Azure/AppConfiguration/blob/main/docs/KVSet/KVSet.v1.0.0.schema.json) that contains all properties of an App Configuration key-value, including key, value, label, content type, and tags.

+- Import Mode: The default value is All. Determines the behavior when importing key-values.

All: Imports all key-values in the configuration file to App Configuration.

Ignore-Match: Imports only settings that have no matching key-value in App Configuration.
+- Dry Run: Default value is Unchecked.

Checked: Prints any updates that would have been performed in a normal run to the console for review.

How about something like ?
Dry Run: Default value is Unchecked.
Checked:  No updates will be performed to App Configuration. Instead, any updates that would have been performed in a normal run will be printed to the console for review.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Using a private repo since a few files need to be updated, sent out a different PR for this change https://github.com/MicrosoftDocs/azure-docs/pull/101868


text:
fix typos in "Event scheduling" section of "Azure Metadata Service: Scheduled Events for Windows VMs"

Disclosure: I am a Microsoft employee.
Changes

fix typo "won't not" and quote "NotBefore"
minor copy editing

@EricRadzikowskiMSFT
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@ShannonLeavitt can I get an exception and have this PR merged? Thanks! #sign-off

source: gharchive/pull-request

authors: ShannonLeavitt cynthn garygurlaskieMSFT

repo: MicrosoftDocs/azure-docs

license_type: permissive

license_source: github-api


text:
Documentation for Azure Batch Start/Deallocate API

Adding documentation that describes and provides information about how to utilize the Batch Start/Deallocate API

@Padmalathas - can you review this new article submission? if you're not the right person, feel free to reassign.
Note that new articles must be merged via the private repo where we have the tools to conduct a full review. (staging and Acrolinx, etc. )  If you approve this, the commits will need to be moved to the private repo and a content contributor will have to take ownership as 'author' and 'ms.author' . Thanks.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

authors: Jak-MS benjaminli-microsoft


text:
Update active-directory-b2c-troubleshoot-custom.md

Replace "Set up" by "Setup".

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@marcelodiiorio : Thanks for your contribution to the Azure documentation! The author, @saeeda, has been notified to review your proposed change.

@marcelodiiorio : Thanks for your contribution to the Azure documentation! The author, @saeeda, has been notified to review your proposed change.

Please see http://grammarist.com/spelling/set-up-vs-setup/

#please-close

authors: PRmerger SaeedAkhter-MSFT marcelodiiorio msftclas


text:
Update data-lake-analytics-u-sql-develop-with-python-r-csharp-in-vsco…

…de.md
CSharp -> C#

@satonaoki : Thanks for your contribution to the Azure documentation! The author, @jejiang, has been notified to review your proposed change.

#sign-off

authors: JennieHubbard PRmerger satonaoki


text:
Update update-device-firmware.md

Fixed formatting on console sample output

@stephen-howell : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; merging. Thanks @stephen-howell

authors: PRMerger9 ktoliver stephen-howell


text:
Update howto-vm-sign-in-azure-ad-windows.md

powershell command prompt is needed to run the troubleshooting steps and not a straight curl command.

@MarkMorow : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @MarkMorow -- This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We'll keep this PR open for review and merge, but in the future, would you make content updates in the private repo? Thanks!

#sign-off


text:
clarify ambiguities in azure authentication/authorisation

These change are primarily geared at making the intention of articles around AAD authentication clearer.
I had quite a bit of confusion around which articles were relevant to enabling Azure authentication on AKS, compared to enabling Azure-defined authorisation. The problem stems from three layers of configuration available on the cluster:

Enabling RBAC at all
Enabling Azure Active Directory
Enabling Azure RBAC
And each one requires the previous one.

The articles are clear to say Kubernetes RBAC, but once I've seen that Azure AD defined RBAC exists, I've been hesitant to alter cluster settings that might enable Azure RBAC, for fear that I can't turn it off again. It's easy to imagine that Kubernetes RBAC was just a misnaming of the deeply integrated offering. As such in my mind, any talk of RBAC was offputting -- I just want authentication.
I also don't really know what the alternatives to AAD authentication are, if any. managed-aad.md talks about the underlying OIDC implementation, and originally managed-aad.md:24 implied there were other non-kubernetes RBAC services available.
Having a place where the config options (both in terms of authn and authz) are clearly enumerated and distinguished as a jumping-off point would go a huge way towards navigating users towards the solution that lets them make the most of AKS.
I still think it's weird to start the managed AAD article talking about the old implementation. But I guess that's just how the article evolved.

Let me know if I should move the comments in my description to an issue. #75299 is perhaps somewhat related.

@michaelruigrok : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@michaelruigrok: I'm sorry - only the author of this article, @mlearned, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


text:
Fix typo

node.js -> Node.js

@changeworld : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

authors: PRMerger3 changeworld msangapu-msft


text:
Updating casing from PUTTY to PuTTY

Updating casing from PUTTY to PuTTY
#96189 is the previous PR that fixed this.

#sign-off

Hi @gatesry , thanks for this fix! I'll look into what happened with the previous PR.

authors: batamig gatesry


text:
Update data-collection-rule-create-edit.md

I believe the descriptions for DCE in the ‘Basic’ tab and the ‘Resources’ tab are swapped.
Could you please check when you have a moment?

@bwren
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Hi @bwren
Gentle Reminder, Could you check this PR when you have time?

repo: MicrosoftDocs/azure-monitor-docs


text:
BootStrapper version

Install-Module -Name AzureRm.BootStrapper -Force should probably include a version

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dabc86bd-3770-5832-7fa5-d28856998ae6
Version Independent ID: cbdb8c6f-ad4d-9e3d-a490-f1348b5ccdfa
Content: Using SQL databases on Azure Stack
Content Source: azure-stack/operator/azure-stack-sql-resource-provider-deploy.md
Service: azure-stack
GitHub Login: @mattbriggs
Microsoft Alias: mabrigg

@lucidqdreams , Thank you for your feedback, We will investigate and get back to you.

#lucidqdreams I've added the current version of Bootstrapper and the requiredversion flag. Thanks for your feedback. The update will be posted with the next doc build. Thanks!

#please-close

source: gharchive/issue

authors: lucidqdreams mattbriggs msrini-MSFT

repo: MicrosoftDocs/azure-stack-docs


text:
merge changes in "master" to "live"

added geographic availability to routing and logistics APIs.
Dietmar and Erik have some changes in masters too.

Docs Build status updates of commit 80cbc45:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/bingmaps-docs, working directory: W:\mfd4-s, target branch: HEAD, target branch commit: 6bd63b04fc7704ecd9425ad0ce71deafd96ff546, source commit: 80cbc45e06ad1ee54e9df4f973410abf6c9e0ef6.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 8fffd3b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/getting-started/bing-maps-dev-center-help/understanding-bing-maps-transactions.md
:warning:Warning
View
Details

BingMaps/rest-services/routes/calculate-a-route.md
:warning:Warning
View
Details

BingMaps/rest-services/routes/optimized-itinerary.md
:warning:Warning
View
Details

BingMaps/rest-services/routes/snap-points-to-roads.md
:warning:Warning
View
Details

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/create-a-load-data-source-job-and-input-entity-data.md
:warning:Warning
View
Details

BingMaps/spatial-data-services/index.md
:warning:Warning
View
Details

BingMaps/spatial-data-services/query-api/query-near-route.md
:warning:Warning
View
Details

BingMaps/articles/create-a-custom-map-url.md
:white_check_mark:Succeeded
View

BingMaps/coverage/geographic-coverage.md
:white_check_mark:Succeeded
View

BingMaps/rest-services/locations/local-search.md
:white_check_mark:Succeeded
View

BingMaps/rest-services/routes/calculate-a-distance-matrix.md
:white_check_mark:Succeeded
View

BingMaps/rest-services/routes/calculate-a-truck-route.md
:white_check_mark:Succeeded
View

BingMaps/rest-services/routes/calculate-an-isochrone.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/android/mapdoubletappedeventargs-class.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/android/mapholdingeventargs-class.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/android/maptappedeventargs-class.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/android/onmaploadingstatuschangedlistener-interface.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/mapelement-class.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/mapelementcollisionbehavior-enumeration.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/mapflyoutcustomviewadapter-interface.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/mapicon-class.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-api/mapview-class.md
:white_check_mark:Succeeded
View

BingMaps/sdk-native/map-control-concepts/display-flyout.md
:white_check_mark:Succeeded
View

BingMaps/spatial-data-services/TOC.yml
:white_check_mark:Succeeded
View

BingMaps/spatial-data-services/public-data-sources/index.md
:white_check_mark:Succeeded
View

BingMaps/spatial-data-services/public-data-sources/navteq-poi-entity-types.md
:white_check_mark:Succeeded
View

BingMaps/spatial-data-services/public-data-sources/navteqeu.md
:white_check_mark:Succeeded
View

BingMaps/spatial-data-services/public-data-sources/navteqna.md
:white_check_mark:Succeeded
View

BingMaps/spatial-data-services/public-data-sources/poi-entity-types.md
:white_check_mark:Succeeded
View

BingMaps/spatial-data-services/public-data-sources/pointsofinterest.md
:white_check_mark:Succeeded
View

BingMaps/spatial-data-services/query-api/query-by-area.md
:white_check_mark:Succeeded
View

BingMaps/getting-started/bing-maps-dev-center-help/understanding-bing-maps-transactions.md

Line 154: [Warning] Link 'https://msdn.microsoft.com/en-us/library/cc981072.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

BingMaps/rest-services/routes/calculate-a-route.md

Line 73: [Warning] Link 'https://msdn.microsoft.com/en-us/library/03ybds8y.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 73: [Warning] Link 'https://msdn.microsoft.com/en-us/library/1k1skd40.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

BingMaps/rest-services/routes/optimized-itinerary.md

Line 1: [Warning] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 4: [Warning] While parsing a block mapping, did not find expected key.

BingMaps/rest-services/routes/snap-points-to-roads.md

Line 157: [Warning] Link 'https://docs.microsoft.com/en-us/bingmaps/rest-services/routes/calculate-a-truck-route' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

BingMaps/spatial-data-services/data-source-management-api/load-data-source-dataflow/create-a-load-data-source-job-and-input-entity-data.md

Line 19: [Warning] Link 'https://msdn.microsoft.com/en-us/library/hh698204.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 54: [Warning] Link 'https://msdn.microsoft.com/en-us/library/dd135733.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 54: [Warning] Link 'https://msdn.microsoft.com/en-us/library/dd135731.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 54: [Warning] Link 'https://msdn.microsoft.com/en-us/library/ee393343.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 59: [Warning] Link 'https://msdn.microsoft.com/en-us/library/ff428642.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 60: [Warning] Link 'https://msdn.microsoft.com/en-us/library/ff428642.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

BingMaps/spatial-data-services/index.md

Line 25: [Warning] Link 'https://msdn.microsoft.com/en-us/library/hh698204.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 27: [Warning] Link 'https://msdn.microsoft.com/en-us/library/ff859477.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

BingMaps/spatial-data-services/query-api/query-near-route.md

Line 19: [Warning] Link 'https://docs.microsoft.com/en-us/bingmaps/v8-web-control/map-control-concepts/spatial-data-services-module-examples/query-api/along-a-route-search' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

repo: MicrosoftDocs/bingmaps-docs


text:
After publishing from Visual Studio, link is giving error.

my Visual Studio says, successfully published.
However, the link that opens says
"
HTTP Error 502.5 - Process Failure
Common causes of this issue:
The application process failed to start
The application process started but then stopped
The application process started but failed to listen on the configured port
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more information visit: https://go.microsoft.com/fwlink/?LinkID=808681"
I don't know what is the problem. At this time, I am simply trying to publish Echo Bot that is in Microsoft Bot Framework Quick Start (from C#). Please help.

@tehmeerali786 - I've seen this error when your Visual Studio project has spaces in its name. Does your project name has spaces?

Thanks. I have made new project with no  spaces on . Now it is giving me another error.
"An error occurred while starting the application.
.NET Core 4.6.26614.01 X86 v4.0.0.0    |   Microsoft.AspNetCore.Hosting version 2.1.1-rtm-30846    |    Microsoft Windows 10.0.14393    |   Need help?"

@tehmeerali786 - the team is investigating similar issues. How did you create your project?

I created from bot builder template v4. Simple echo bot.
But, the tutorials I have watched and textbooks all of them show some bot template coming on project dialog. But now it appears on column. And, it does not create the same bot files that were created in textbooks printed few months ago. Why Microsoft is doing drastic changes in Syntax and

repo: MicrosoftDocs/bot-docs


text:
Bullet needed for SetAccessors

In 'How the state property accessor methods work' section, another bullet is required for set accessors.
I am also not able to edit this particular file in GitHub because of 404 error. Kindly have a look.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a1795c22-9e0f-8a69-a517-ffbe38a2cd30
Version Independent ID: 9d2c1569-6d6f-97fa-881d-b4a0f61623a2
Content: Managing State - Bot Service
Content Source: articles/v4sdk/bot-builder-concept-state.md
Service: bot-service
Product: bot-framework
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

Closing it as I have found it fixed in live-sync branch.


text:
What are the several other channels available?

The documentation says:

You can connect to many popular services, such as Cortana, Facebook Messenger, Kik, and Slack, as well as several others.

But there is no full list of those "several others".

The most accurate list is in the Azure portal. For details, see: https://docs.microsoft.com/en-us/azure/bot-service/bot-service-manage-channels?view=azure-bot-service-4.0.

Looks like I pasted the wrong link but the quote is from that page you posted. In any case, what I am understanding is that I need to create an account to be able to see the most accurate up to date list, probably not the most optimal for people trying to asses if the framework is suitable for their project.

authors: Kaiqb juanpdelat


text:
Update bot-builder-create-templates.md

Removing all reference to Java, because the BotBuilder is not fully functional for Java developers.  The current java support is useless and misleading to Java users who may be struggling to get it to work.

Removed java reference

repo: MicrosoftDocs/bot-framework-docs


text:
Step 2 leads to a page that leads to a 404

Step 2 of the checklist links to an e-book download site (Containerize your Apps with docker and Kubernetes).
On that download site, after filling the form, a 404 is returned. just thought of letting you know, it's a little broken and maybe we're better off removing the link to the e-book if we can tfind owner?
Thanks, Eyas

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d04bb23f-c4d6-ee39-0843-084b1411328b
Version Independent ID: 5aba2c57-770d-4bed-c178-44cd05aab9c2
Content: Application development and deployment - Cloud Adoption Framework
Content Source: docs/innovate/kubernetes/application-development.md
Service: cloud-adoption-framework
Sub-service: innovate
GitHub Login: @sabbour
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 376038

This issue has been resolved.

authors: JanetCThomas eyast

repo: MicrosoftDocs/cloud-adoption-framework


text:
Forward binary comaptibility guarantees?

In this topic: https://github.com/MicrosoftDocs/cpp-docs/blob/master/docs/porting/binary-compat-2015-2017.md there used to be explicit guarantee for backwards binary compatibility (still there) and explicit denial of forward binary compatibility:

When consuming libraries built with a toolset whose version is greater than the toolset used to compile and link the application. For example, a program that is compiled and linked with compiler version 19.12 can consume libraries that are compiled with 19.0 up through 19.12. Also, binary compatibility only exists between Visual Studio 2015 and Visual Studio 2017; linking 19.x programs with libraries produced by Visual Studio 2013 or earlier is not supported.

The latter is no longer there. Along with wording such as

The runtime libraries and apps compiled by any of these versions of the compiler are binary-compatible.

it might lead to incorrect assumptions that forward binary compatibility is indeed supported. I do not thing it is the case and removal of the first quoted paragraph was wrong and decreased clarity of the topic. If the forward binary compatiblity is indeed NOT guaranteed (as I suspect and as it used to be for a long time) then the topic should definitely say so explicitly.

@Resurr3ction
By coincidence, I made a change in this article yesterday, which may address your issue. Please take a look at the current content, and see if it answers your question about forward compatibility. There's a new distinction made between the toolset version used for compiling, and the one used for linking, for forward binary compatibility that wasn't in the article previously. Basically, an old app can consume a newer static library without being recompiled, as long as it's relinked using the newer linker. This isn't a new feature, but it wasn't described correctly in the paragraph you quote, either.

@corob-msft It actually does! At our organization what we are doing is delivering newer binaries to older releases. When they came from the same compiler/linker it was not a problem. Now when we upgrade to a newer compiler we would like to know whether this is still a safe practice. I assumed not based on the original quote. But now it is quite clear I believe. Recompilation would not be needed but relinking would. Thank you.

@Resurr3ction
I'm glad that worked out. I thought it was funny how your comment came in not long after I'd made the change, but before it was visible. Prescient!

repo: MicrosoftDocs/cpp-docs


text:
Repo sync for protected CLA branch

The pull request is created from main638089885318570234sync_temp to main to fix git push error for protected CLA branch

Learn Build status updates of commit 3daf1ba:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

repo: MicrosoftDocs/dataexplorer-docs


text:
Broken link in Project tasks / Milestones resources

Hi, Please update the link to the resources for project milestones and tasks. for e.g: It is pointing to https://ax.help.dynamics.com/wiki/<resource>/   this then redirects to the current dynamics 365 for operations home page https://docs.microsoft.com/en-au/dynamics365/unified-operations/fin-and-ops/

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 839b8149-3604-a6e2-cb3a-63531a789de8
Version Independent ID: 0293a176-32e9-156f-ad43-478544963e93
Content: Projects in Lifecycle Services (LCS) - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/lifecycle-services/ax-2012/projects-lcs.md
Product: dynamics-ax-2012
GitHub Login: @manalidongre
Microsoft Alias: manado

Thanks for your suggestion, however there aren't any links in the Projects in Lifecycle Services topic that point to milestones or tasks. Can you provide specific information about where you are encountering broken links.

Please check the attached screenshot from LCS

Thanks

This has been resolved

authors: manishmoothedath tonyafehr


text:
This link to the documentation is no longer valid

For more information, see SAF-T - VMI.
The updated one is https://www.vmi.lt/evmi/en/home

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 132df4cc-1a93-896a-5551-dbed3cc7f4af
Version Independent ID: b37b12a7-ea57-57f3-59c4-585630c85b40
Content: Standard Audit File for Tax (SAF-T) for Lithuania - Finance | Dynamics 365
Content Source: articles/finance/localizations/emea-ltu-saf-t.md
Service: dynamics-365-finance
Product: ****
Technology: ****
GitHub Login: @liza-golub
Microsoft Alias: elgolu

@liza-golub and @kfend  - Can you verify and replace the link? Thanks.

Created bug 594447 to track this issue.

The link is fixed.

authors: RobinARH TimoTenni


text:
Remove "Preview" from the title

I guess you can remove the word "Preview" from title by now.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: caa7bcc6-0bba-b6f3-d20e-92ac4cccdb32
Version Independent ID: 0b2db86c-e326-febc-1443-cbac2f776887
Content: What's new or changed in Dynamics 365 Finance 10.0.19 (June 2021) - Finance | Dynamics 365
Content Source: articles/finance/get-started/whats-new-changed-10-0-19.md
Service: dynamics-365-finance
Product: ****
Technology: ****
GitHub Login: @roschlom
Microsoft Alias: roschlom

@PalleAgermark - thank you for the feedback. I have updated the topic and the changes will be published later today.

authors: PalleAgermark kfend


text:
Enhanced e-Commerce product discovery to be inventory-aware doesn't support multiple fulfillment location

Enhanced e-Commerce product discovery to be inventory-aware considers stock of  warehouse assigned to Online store only. If you use DOM or have multiple fulfillment warehouses or use aggregate of stock from multiple warehouses to calculate inventory availability in Ecommerce this feature will not provide the accurate information. To avoid confusion, the article should be updated to explain how the attributes will be updated to show an item as available or out of stock.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b49084e9-8f21-21f2-bff0-f9cdcd62bd4a
Version Independent ID: 216ebb58-9e0d-295a-3396-ca0e3bd3af7c
Content: Search results module - Commerce | Dynamics 365
Content Source: articles/commerce/search-result-module.md
Service: dynamics-365-commerce
Product: ****
Technology: ****
GitHub Login: @anupamar-ms
Microsoft Alias: anupamar

@5fq, thank you for providing this feedback.
@anupamar-ms, please update the content as suggested.

Bug 693419 has been logged to track this issue.

Closed as won't fix.


text:
Correct link in Description section

Instead of a link, we see [/dynamics365/business-central/dev-itpro/compliance/apptest-countries-and-translations]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 12419013-90c4-b413-eb21-47f2873a88aa
Version Independent ID: f92a516c-815f-0510-bf47-533e361c0e3e
Content: The country codes specified in the 'supportedCountries' property must be valid ISO 3166-1 alpha-2 codes - Business Central
Content Source: dev-itpro/developer/analyzers/appsourcecop-as0056-appsourcecopconfigurationsupportedcountriesmustbevalidcountrycode.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: SusanneWindfeldPedersen

Thanks for catching this bug. It will be fixed with the next doc refresh. Thanks.

authors: NKarolak SusanneWindfeldPedersen


text:
Wrong translation of Unit Price: Einheitspreis

There is a wrong translation of Unit Price: Einheitspreis. In German BC it is called „VK-Preis” oder “Verkaufspreis”.

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 9e6c90a8-22c7-8572-195c-b77237a765e8
Version Independent ID: ebae59fd-cb1e-1da4-80d3-b5afaf712df8
Content: Buchungsdatum auf Wertposten - Business Central
Content Source: business-central/design-details-inventory-adjustment-value-entry-posting-date.md
Service: dynamics365-business-central
GitHub Login: @edupont04
Microsoft Alias: edupont

Thanks! Submitting to the translation team.


text:
Trim()

[Enter feedback here]
There is an option of Trim() within the "Manage Transformation" page.
However, Trim is not listed on this documentation page and the Trim transform appears to not work.
For product feedback - the Replace Regex transform page allows the transform to be tested, that would be useful for other transforms where that is currently not available.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 4c350829-8476-71a7-f53b-6cf788917037
Version Independent ID: fbab99b8-0e94-1075-cb38-11a972feba87
Content: Customize SAML token claims - Microsoft identity platform
Content Source: docs/identity-platform/saml-claims-customization.md
Service: identity-platform
GitHub Login: @cilwerner
Microsoft Alias: cwerner

@alicain
Thank you for bringing this to our attention.
I've delegated this to content author @cilwerner, who will review it and offer their insightful opinions.

We are in the process of transferring to a new unified user feedback system. This issue is being triaged and added to the backlog where it will be addressed in an upcoming sprint.
#please-close

authors: Naveenommi-MSFT alicain cilwerner

repo: MicrosoftDocs/entra-docs

license: MIT


text:
Update certificate-credentials.md - do not advertise unsecure hash and signing algorithms

x5t is not recommended, because it uses SHA1. x5t#sha256 is recommended
RS256 implies using PKCS1 padding, which is also not recommended. PS256 corresponds to PSS padding, which is supported.
This is what recent versions of MSAL libs do.
In in doubt, please contact the Microsoft Crypto board or myself

@OwenRichards1
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

authors: OwenRichards1 ShannonLeavitt bgavrilMS


text:
Token Admin documentation on Azure DevOps REST API is not complete

I am trying to work out how to use the Token Admin "Revoke Personal Access Token" functionality of the Azure DevOps REST API's. However - most of the functionality is not documented in enough detail to understand how to use it.
An example is the page referenced above. It should be possible to revoke a token, but there is not enough documentation for the "Request Body" to understand how. It just says that the body is a string.
I have tried to guess how to use it - one of the guesses was to use this as the body:
[
  {
    "authorizationId": "<GUID authorizationId from existing PAT>"
  }
]

But it throws this error:
{
    "$id": "1",
    "innerException": null,
    "message": "Parameter 'accessTokenKey' cannot be omitted",
    "typeName": "Microsoft.VisualStudio.Services.TokenAdmin.Client.TokenAdminBadRequestException, Microsoft.VisualStudio.Services.WebApi",
    "typeKey": "TokenAdminBadRequestException",
    "errorCode": 0,
    "eventId": 3000
}

Please update the documentation such that it is possible to understand how to use the REST API's.

@jlundstocholm Please move this issue to https://github.com/MicrosoftDocs/azure-devops-docs/issues

@jlundstocholm Please move this issue to https://github.com/MicrosoftDocs/azure-devops-docs/issues

Done :-)
https://github.com/MicrosoftDocs/azure-devops-docs/issues/11265

authors: jlundstocholm rootsmusic

repo: MicrosoftDocs/feedback


text:
Collaborating on a liveshare doc

Product and Version [VS/VSCode]: 1.38.1
OS Version [macOS/Windows/Linux]: Windows
Live Share Extension Version: 1.0.0.905
Target Platform or Language [e.g. Node.js]: Node.js
What were you doing when you encountered the desync?
Collaborating on app.js and index.html files
How often have you encountered desyncs?
We've had several in the past few minutes. Over the past several weeks, we've encountered similar issues numerous times. If a file is deleted or created, that seems to trigger it to desync, but we also have just encountered where it's never synced in the first place. When we initially connected today and the host shared the server and terminal, one collaborator could see both and I could not see either until I disconnected and reconnected.

@KireniaV Thanks for reaching out. @daytonellwanger can you take a look at this  ?

Hey @KireniaV , we're actively looking into this, and will hopefully have some fixes released in the next several weeks. At that point, I'll follow back up to see if they've resolved your issues.

Closing this as a duplicate of #2086.

authors: KireniaV daytonellwanger lostintangent setaskin

repo: MicrosoftDocs/live-share


text:
[VS Code] Could not load file or assembly 'System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.

crash.zip

Error:
Could not load file or assembly 'System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.
Steps to Reproduce:

Install extension

Login

Try to share a link

Version Data

extensionName
VSLS

extensionVersion
0.3.295

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.21.1

platformName
MacOS

platformVersion
17.6.0

Thanks for letting us know about this issue. This is likely due to a bad install of the VSLS extension. If you haven't already, can you try uninstalling the VS Live Share extension & reinstalling it again? Can you also confirm what version of MacOS you're using (ex:  10.13 High Sierra)?

I closed and reopened visual studio and the issue resolved itself.
On Tue, Jun 19, 2018, 10:34 AM jramsay notifications@github.com wrote:

Thanks for letting us know about this issue. This is likely due to a bad
install of the VSLS extension. If you haven't already, can you try
uninstalling the VS Live Share extension & reinstalling it again? Can you
also confirm what version of MacOS you're using (ex: 10.13 High Sierra)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/live-share/issues/566#issuecomment-398482194,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkQHWr8xOG0ppHFaDNDrdD3jGd8XPLaks5t-TYVgaJpZM4Ut5K3
.

@roshkins That's great to hear! Let us know if this issue appears again. In the meantime, I'm going to close it as a duplicate as #362. Thanks!

authors: jramsay lostintangent roshkins


text:
New content, updates.

Category

[X] New article

Docs Build status updates of commit 6bba0e9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/defining-a-power-platform-data-loss-prevention-strategy.md
:warning:Warning
View
Details

Community/defining-a-power-platform-environment-strategy.md
:warning:Warning
View
Details

Community/glossary.md
:warning:Warning
View
Details

Community/auto-apply-retention-labels-in-office-365-using-content-types-and-metadata.md
:white_check_mark:Succeeded
View

Community/designing-solution-for-scale.md
:white_check_mark:Succeeded
View

Community/document-lifecycle-scenarios.md
:white_check_mark:Succeeded
View

Community/empowering-your-SharePoint-champions.md
:white_check_mark:Succeeded
View

Community/evolution-of-company-wide-email-communication-to-sharepoint-news.md
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/news-digest.png
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/org-news.png
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/persistent-news.png
:white_check_mark:Succeeded
View

SharePoint-News
:white_check_mark:Succeeded

Community/defining-a-power-platform-data-loss-prevention-strategy.md

Line 4, Column 9: [Warning-author-not-found] Invalid value for author: 'Aaron Rendell' is not a valid GitHub ID.
Line 27, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

Community/defining-a-power-platform-environment-strategy.md

Line 4, Column 9: [Warning-author-not-found] Invalid value for author: 'Aaron Rendell' is not a valid GitHub ID.
Line 87, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/power-platform/admin/environments-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

Community/glossary.md

Line 294, Column 3: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 297, Column 0: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/power-platform/admin/environments-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 284, Column 1: [Suggestion-merge-conflict] File contains merge conflict markers. NOTE: This Suggestion will become a Warning on 06/30/2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 197d697:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/auto-apply-retention-labels-in-office-365-using-content-types-and-metadata.md
:white_check_mark:Succeeded
View

Community/defining-a-power-platform-environment-strategy.md
:white_check_mark:Succeeded
View

Community/designing-solution-for-scale.md
:white_check_mark:Succeeded
View

Community/document-lifecycle-scenarios.md
:white_check_mark:Succeeded
View

Community/empowering-your-SharePoint-champions.md
:white_check_mark:Succeeded
View

Community/evolution-of-company-wide-email-communication-to-sharepoint-news.md
:white_check_mark:Succeeded
View

Community/glossary.md
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/news-digest.png
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/org-news.png
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/persistent-news.png
:white_check_mark:Succeeded
View

SharePoint-News
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f8f1cb9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/auto-apply-retention-labels-in-office-365-using-content-types-and-metadata.md
:white_check_mark:Succeeded
View

Community/defining-a-power-platform-environment-strategy.md
:white_check_mark:Succeeded
View

Community/designing-solution-for-scale.md
:white_check_mark:Succeeded
View

Community/document-lifecycle-scenarios.md
:white_check_mark:Succeeded
View

Community/empowering-your-SharePoint-champions.md
:white_check_mark:Succeeded
View

Community/evolution-of-company-wide-email-communication-to-sharepoint-news.md
:white_check_mark:Succeeded
View

Community/glossary.md
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/news-digest.png
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/org-news.png
:white_check_mark:Succeeded
View

Community/media/evolution-of-company-wide-email-communication-to-sharepoint-news/persistent-news.png
:white_check_mark:Succeeded
View

SharePoint-News
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


text:
edits

Category

[X] Content fix, updates

Docs Build status updates of commit 4c9a757:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/glossary.md
:warning:Warning
View
Details

Community/TOC.md
:white_check_mark:Succeeded
View

Community/defining-a-power-platform-environment-strategy.md
:white_check_mark:Succeeded
View

Community/document-lifecycle-scenarios.md
:white_check_mark:Succeeded
View

Community/index.yml
:white_check_mark:Succeeded
View

Community/known-folder-move-benefits-for-enduser.md
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario01-Personal-Productivity.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario02-DepartmentEnvironments.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario03-ApplicationEnvironments.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario04-Multi-Tenant.png
:white_check_mark:Succeeded
View

Community/glossary.md

Line 181, Column 267: [Warning-bookmark-not-found] Cannot find bookmark '#OneDrive-PC-Folder-Backup' in 'glossary.md'.
Line 237, Column 39: [Warning-bookmark-not-found] Cannot find bookmark '#Known-Folder-Move-KFM' in 'glossary.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2a6012f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/glossary.md
:warning:Warning
View
Details

Community/TOC.md
:white_check_mark:Succeeded
View

Community/defining-a-power-platform-environment-strategy.md
:white_check_mark:Succeeded
View

Community/document-lifecycle-scenarios.md
:white_check_mark:Succeeded
View

Community/index.yml
:white_check_mark:Succeeded
View

Community/known-folder-move-benefits-for-enduser.md
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario01-Personal-Productivity.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario02-DepartmentEnvironments.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario03-ApplicationEnvironments.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario04-Multi-Tenant.png
:white_check_mark:Succeeded
View

Community/glossary.md

Line 181, Column 267: [Warning-bookmark-not-found] Cannot find bookmark '#oneDrive-pc-folder-backup' in 'glossary.md', did you mean '#onedrive-pc-folder-backup'?

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit ce835ac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/TOC.md
:white_check_mark:Succeeded
View

Community/defining-a-power-platform-environment-strategy.md
:white_check_mark:Succeeded
View

Community/document-lifecycle-scenarios.md
:white_check_mark:Succeeded
View

Community/glossary.md
:white_check_mark:Succeeded
View

Community/index.yml
:white_check_mark:Succeeded
View

Community/known-folder-move-benefits-for-enduser.md
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario01-Personal-Productivity.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario02-DepartmentEnvironments.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario03-ApplicationEnvironments.png
:white_check_mark:Succeeded
View

Community/media/defining-a-power-platform-environment-strategy/Scenario04-Multi-Tenant.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


text:
Information on deleting domains incorrect?

Is the Note at point 4 in this section "Add a new onmicrosoft.com domain" https://learn.microsoft.com/en-us/microsoft-365/admin/setup/add-or-replace-your-onmicrosoftcom-domain?view=o365-worldwide&source=docs#add-a-new-onmicrosoftcom-domain
correct?

From what I can see in the Azure portal deletion of onmicrosoft.com domains is possible:

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 0a66bd91-6de1-5128-0f77-df1573b7f800
Version Independent ID: 0a66bd91-6de1-5128-0f77-df1573b7f800
Content: Add and replace your onmicrosoft.com fallback domain in Microsoft 365 - Microsoft 365 admin
Content Source: microsoft-365/admin/setup/add-or-replace-your-onmicrosoftcom-domain.md
Service: microsoft-365-business
GitHub Login: @efrene
Microsoft Alias: efrene

I followed up with engineering on this.  They verified that although you will see the Delete button in the Azure portal, if you attempt to continue with deleting the verified onmicrosoft.com domain, it will fail with an error.

I followed up with engineering on this. They verified that although you will see the Delete button in the Azure portal, if you attempt to continue with deleting the verified onmicrosoft.com domain, it will fail with an error.

@efrene - please provide the following feedback to the engineering team:
As a general principle, if something is not possible to be done, then
a) clear information should be provided in the GUI regarding what is possible/not possible, and
b) options (menus, buttons etc) to manage a resource should be consistent with what is possible - i.e. no delete button or menu item should be available or should be deactivated.
In this instance,
o	Options to delete the domain are clearly visible
o	All the processes to prepare for deletion of this domain are available
o	When reaching the final step for deletion, the error message does not provide correct/clear information
All of this is contrary to what is apparently actually possible. No information is provided anywhere regarding that this domain cannot be deleted.
This is a very poor user experience and a waste of my time, my customer’s time, and Microsoft support resources time.
Not only is it a waste of time it is extremely frustrating for me and my customer. Microsoft needs to continually pay attention to and ensure good usability at all times.

authors: a-goo efrene


text:
'Customize the email subject' topic missing

[Enter feedback here]
'Customize the email subject' topic is missing so no idea how to customize, what are those variables to use to make subject email customization dynamic like 'customize the email text' topic where dynamic variables can be use.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0505aba8-2455-5390-b34b-6bb0865b14db
Version Independent ID: 401701a8-86fd-8570-8084-33622f34bb91
Content: Send email notifications and show policy tips for DLP policies - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/use-notifications-and-policy-tips.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

@mevaibhav83 Thank you for your feedback. Currently, we do not have an option to customize the subject. However, this design change has been requested via UserVoice- https://office365.uservoice.com/forums/928576-microsoft-information-protection-mip/suggestions/33556768-allow-customization-for-sender-and-subject-for-cus and you can upvote this design change to be notified when this change goes live.
Hope this helps!
@yogkumgit There are no changes required in this document and the issue can be closed.
Thanks
Sri

@mevaibhav83 Thank you for your feedback. Currently, we do not have an option to customize the subject. However, this design change has been requested via UserVoice- https://office365.uservoice.com/forums/928576-microsoft-information-protection-mip/suggestions/33556768-allow-customization-for-sender-and-subject-for-cus and you can upvote this design change to be notified when this change goes live.
Hope this helps!
@yogkumgit There are no changes required in this document and the issue can be closed.
Thanks
Sri

@mevaibhav83  Thank you very much for your kind feedback. Considering your valuable feedback, as advised please vote for this User Voice. Concerning team will evaluate and take the appropriate action, as per their schedule. We proceed here to close it. Thanks again for taking out some time and sharing your feedback.

@mevaibhav83  Thank you very much for your kind feedback. Considering your valuable feedback, as advised please vote for this User Voice. Concerning team will evaluate and take the appropriate action, as per their schedule. We proceed here to close it. Thanks again for taking out some time and sharing your feedback.

authors: mevaibhav83 msbemba yogkumgit


text:
Deleting unlicensed user after shared mailbox is created

Hi, this is more of a question,
What happens if I delete the user after the shared mailbox has been created after a month?
Will the shared mailbox still be there?
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4e366b9c-0d35-83c6-f509-1774dd351504
Version Independent ID: 702f2dc1-46f8-508a-68bc-b5d033c56a9a
Content: Remove a former employee - Microsoft 365 admin
Content Source: microsoft-365/admin/add-users/remove-former-employee.md
Service: o365-administration
GitHub Login: @KwekuA
Microsoft Alias: kwekua

@ramire-cc Thank you for your feedback. The Shared mailbox gets purged as soon as the linked unlicensed user account is deleted from the admin center. They are linked and the user when deleted can still be retrieved for the next 30 days.
Hope this helps!
Thanks
Sri

Hi Sri,
Thank you for the response.
So to confirm, if the user is deleted from admin center, so as the shared mailbox’s contents?
I have a shared mailbox on my desktop outlook that I set-up when an employee left. The user is already unlicensed and I don’t see new emails coming in.
Now I want to delete the user completely from admin center but want to keep the shared mailbox contents.
Can I proceed in doing it?
Regards,
[Image]
Ramir Enriquez
Cloudster Connect
a:
Australia, The Philippines, India
w:
www.cloudsterconnect.cohttp://www.cloudsterconnect.co/  e: @.@.>
From: Sriraman M S @.>
Sent: Tuesday, 16 March 2021 3:32 AM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Ramir Enriquez @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Deleting unlicensed user after shared mailbox is created (#4407)
@ramire-cchttps://github.com/ramire-cc Thank you for your feedback. The Shared mailbox gets purged as soon as the linked unlicensed user account is deleted from the admin center. They are linked and the user when deleted can still be retrieved for the next 30 days.
Hope this helps!
Thanks
Sri
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/4407#issuecomment-799694775, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APOCZ3AXEYW4WJMP52OXRSLTDZOB7ANCNFSM4Y7NM37Q.

@ramire-cc While that is possible, the approach needs to be a little different. I'd suggest you to contact Microsoft support via the need help section so that they can help you sort this out.
Thanks
Sri

@msbemba  Thank you very much for the contribution and sharing this explanation. @ramire-cc Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed here to close it.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

authors: msbemba ramire-cc yogkumgit


text:
High resolutions picture addition

As requested by user, high resolutions pictures has been added.
Problem: https://github.com/MicrosoftDocs/microsoft-365-docs/issues/845

@MSFTTracyP  this is for https://github.com/MicrosoftDocs/microsoft-365-docs/issues/845 -- Can you confirm the images work.

authors: LauraWi joinimran


text:
Update manage-deployment-of-add-ins.md

Updated the navigation to reflect the new option integrated apps

@JohanFreelancer9 PLease copy review
per issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/9288

Docs Build status updates of commit f078b9f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/manage-deployment-of-add-ins.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@kwekuako Please merge this PR. Thanks

Docs Build status updates of commit fca0d47:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/manage-deployment-of-add-ins.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8629f72:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/manage-deployment-of-add-ins.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8629f72:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/manage/manage-deployment-of-add-ins.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


text:
Update microsoft-365-docs-navigation-guide.md

Fixed broken link.

Docs Build status updates of commit fc206f8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-365/microsoft-365-docs-navigation-guide.md
:warning:Warning

Details

microsoft-365/microsoft-365-docs-navigation-guide.md

Line 61, Column 3: [Warning: link-out-of-scope] File '../README.md' referenced by link '../README.md' will not be built because it is not included in build scope.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Copy review - I do not see the need for this change. The original link seems to work fine. Thanks.

huh, that's odd. I dunno why it does not on my end 😕

There isn't a directory named contribute inside microsoft-365-docs/microsoft-365/ so I'm not sure how that link is working. In any case, if you want me to close this PR, I'll do it.

Docs Build status updates of commit f2b4f69:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

welp, the relative link does work if I edit it in the public branch and see the diff.

Hi @mdanish-kh. Thanks again for your input. However, I have tested again and the original link does work It links to https://docs.microsoft.com/en-us/contribute/. So I would suggest you kindly close this PR. Many thanks.

Oh, I'm dumb. I should've checked this on the main webpage instead of the github repo. Sorry for the inconvenience.

Docs Build status updates of commit f2b4f69:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/microsoft-365-docs-navigation-guide.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Hi @mdanish-kh. Thanks again for your input. However, I have tested again and the original link does work It links to https://docs.microsoft.com/en-us/contribute/. So I would suggest you kindly close this PR. Many thanks.

Oh, I'm dumb. I should've checked this on the main webpage instead of the github repo. Sorry for the inconvenience.

No problem at all.


text:
[Script-API] [Feature Request] console.log() for console output on BDS

Is your feature request related to a problem? Please describe.
There is no way to directly send an output console message on Bedrock Dedicated Server to the server terminal.
Describe the solution you'd like
Use for console.log() function to output to the server terminal.
Describe alternatives you've considered
console.warn() to output to the content log file or world.say() to output to the chat which aren't as convenient to use as direct console output.
Additional context
None

maybe New Module what will be avialable on BDS only, so maybe features like readLine and write/writeLine, could be useful.

Thank you for your issue. Sorry to hear you are having trouble. We are unable to provide general support via this feedback channel that isn’t related to specific documentation issues.

repo: MicrosoftDocs/minecraft-creator


text:
Update using-the-hololens-emulator.md

Updating Emulator two download link to download the latest version.

Docs Build status updates of commit f2683f4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/using-the-hololens-emulator.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

repo: MicrosoftDocs/mixed-reality


text:
Build pipeline

Creating pull request

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: rajenshahu sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

authors: msftclas rajenshahu


text:
Build jyable

ok

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: okoudje sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Pull Request create by mistake. It's azure DevOps sample Exercice

authors: msftclas okoudje


text:
Error in document

Hi there,
There is a defect in following mentioned link.
https://msdn.microsoft.com/en-us/library/microsoft.owin.security.oauth.oauthauthorizationserverprovider(v=vs.113).aspx
Please scroll to "Properties" and go to "OnGrantCustomExtension".
I believe that word "andpoint" in line "Called when a request to the Token andpoint arrives with a "grant_type" of any other value" should be written as "endpoint".
Thanks,
Jai

Unfortunately the file isn't under our control so we can't fix it.

authors: billbliss jaisendmehtc

repo: MicrosoftDocs/msteams-docs


text:
Live

Push to live: test PR

Docs Build status updates of commit 6b5c75b:
:warning: Validation status: warnings
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

test PR


text:
Experimental Feature?

When I run the Set-PnPHomeSite command, I get the following error:
"Set-PnPHomeSite : The requested operation is part of an experimental feature that is not supported in the current
environment."
I was under the impression this was pushed.  Am I just too early, or is there really an issue?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 12da9c12-7eff-f43f-67ff-d667d12847d4
Version Independent ID: bf90101d-939a-08b0-79fd-1032f00eccc7
Content: Set-PnPHomeSite (sharepoint-pnp)
Content Source: sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPHomeSite.md
GitHub Login: @techwriter40
Microsoft Alias: kirks

@officedocsbot assign @yogkumgit

Hello @Anonimiss Thanks for your feedback.
PnP cmdlets as you might know, are a community-driven effort and are constantly evolving, the documentation for the PnP cmdlets is directly synchronized from the source code in this repo so if a new cmdlet is created there, there will be an article here, even though the feature can be experimental and in development. So there is no really an issue, it is just not ready yet.
Hope this information helps you. Thanks again

@get-itips  Thank you very much for the contribution and sharing this explanation. @Anonimiss
Hope this comment is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

authors: Anonimiss get-itips yogkumgit

repo: MicrosoftDocs/office-docs-powershell


text:
Needs info on potential wait time

Though executing the PowerShell is quick, it seems that it actually takes some time for the new Org Assets Library to show up for users.
I've created two and Get-SPOOrgAssetsLibrary reports the existence of both, but I've been waiting ~10 minutes for my second one to show up.
How long should I wait before assuming there was a problem?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b8deb61c-91a1-7e4c-cf56-d682026c6011
Version Independent ID: 7d8c994d-8673-27dc-04ab-3c5c104c0daa
Content: Add-SPOOrgAssetsLibrary (sharepoint-online)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Add-SPOOrgAssetsLibrary.md
Service: sharepoint-powershell
GitHub Login: @Maralesfahanpoor
Microsoft Alias: maesfaha

@officedocsbot assign @yogkumgit

Hi Jim,
I've seen it take anywhere from an hour to almost a full day for the assets library to start showing up for users. I noticed your comment was from a couple days ago, is it still not showing up?
Thanks!
Rachel

It is there now, yes.
Get Outlook for Androidhttps://aka.ms/ghei36

From: RachelLambert34 notifications@github.com
Sent: Monday, September 30, 2019 10:33:26 AM
To: MicrosoftDocs/office-docs-powershell office-docs-powershell@noreply.github.com
Cc: Jim Duncan sparchitect@live.com; Author author@noreply.github.com
Subject: Re: [MicrosoftDocs/office-docs-powershell] Needs info on potential wait time (#4068)
Hi Jim,
I've seen it take anywhere from an hour to almost a full day for the assets library to start showing up for users. I noticed your comment was from a couple days ago, is it still not showing up?
Thanks!
Rachel
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/office-docs-powershell/issues/4068?email_source=notifications&email_token=ACGHYGC4UETCN3J23GRHIV3QMIZ6NA5CNFSM4I3MAN22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD76OF4Y#issuecomment-536666867, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACGHYGH3S6SRWF3ROPP6UELQMIZ6NANCNFSM4I3MAN2Q.

@get-itips  Thank you very much for the contribution and updating the documentation with PR. @sparkitect Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

authors: RachelLambert34 sparkitect yogkumgit


text:
KeySize parameter correction

The KeySize parameter has both 1024 and 2048 as accepted values, atleast per version 1.1.166.0 of the MSOnline module.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bd23aab2-5378-59a2-951f-3d808871f872
Version Independent ID: fef7c224-f830-5056-685d-c2b61ec22c6c
Content: Rotate-DkimSigningConfig (exchange)
Content Source: exchange/exchange-ps/exchange/antispam-antimalware/Rotate-DkimSigningConfig.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

@dariomws306  Thank you very much for the contribution and updating the documentation with PR. @Lsvingen Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

authors: Lsvingen yogkumgit


text:
PowerShell examples are missing $PSItem in foreach Loop

Incorrect Sample: $NPS | foreach {Set-User -RemotePowerShellEnabled $false}
Corrected Sample: $NPS | foreach {Set-User  $_ -RemotePowerShellEnabled $false}
If you are using a Object as input: Then we need to select
$DSA | foreach {Set-User  $_.Name  -RemotePowerShellEnabled $false}
$_ or $PSItem needs to be used to reference the item passed via the Pipe.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d03c6ce2-687b-e138-939b-413014d1c81a
Version Independent ID: 9fe6c492-d0fe-e454-6574-06de8cd31a21
Content: Control remote PowerShell access to Exchange servers
Content Source: exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@satyajit321, topic updated.
Thanks for the feedback.
Closing


text:
Update Add-TeamUser.md

https://github.com/MicrosoftDocs/office-docs-powershell/issues/1665

Docs Build status updates of commit 74a4e5d:
:clock10: Full build: the average full build time is 14 min(s) 11 sec(s), this is based on the last 335 build(s) for this repository.

Docs Build status updates of commit 74a4e5d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Add-TeamUser.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
Flow vs Power Automate

Notes still listed about the name change however I believe documentation has been updated already

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e9d12f42-d17f-647e-b25c-ef6e56167983
Version Independent ID: de5ec638-fffb-bd32-ee7c-66928026aa1c
Content: Find and fix errors with the Power Automate checker - Power Automate
Content Source: articles/error-checker.md
Service: flow
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@sth2258 Thanks for the comment. Yes, we are aware of this but persisting with the message a little longer. We'll soon remove the note.
Closing the issue.

repo: MicrosoftDocs/power-automate-docs


text:
fetchxml Results attribute

https://docs.microsoft.com/en-us/powerapps/maker/portals/liquid/template-tags#results-attribute
this section defines several additional attributes available from the Results attribute:
Entities, EntityName, ExtensionData, MinActiveRowVersion, MoreRecords, PagingCookie, TotalRecordCount, TotalRecordCountLimitExceeded
Only Entities seems to return any data.  I have tried the following example and cannot retrieve any of the Results attribute details:
{%- fetchxml contacts -%}
<fetch returntotalrecordcount="true">
  <entity name="contact" >
    <attribute name="firstname" />
    <attribute name="lastname" />
    <attribute name="contactid" />
    <filter type="and" >
      <condition attribute="statecode" operator="eq" value="0" />
    </filter>
  </entity>
</fetch>
{%- endfetchxml -%}
{%- if user -%}
    EntityName: {{-contacts.results.entityname-}}

    ExtensionData: {{-contacts.results.ExtensionData-}}

    MinActiveRowVersion: {{-contacts.results.MinActiveRowVersion-}}

    MoreRecords: {{-contacts.results.MoreRecords-}}

    PagingCookie: {{-contacts.results.PagingCookie-}}

    TotalRecordCount: {{-contacts.results.TotalRecordCount-}}

    TotalRecordCountLimitExceeded: {{-contacts.results.TotalRecordCountLimitExceeded-}}

    XML: {%-assign e=contacts.XML-%}{{-e | escape-}}
{%- endif -%}

I've tried changing the case of the attributes and even changing scope back to the contacts object, but no luck.  I tried assigning each to a variable then rendering the variable value, but no luck.
In the above example, only contacts.XML and contacts.results.entities.size render any information.
Do these attributes actually serve up data?

Thank you for reaching out. For issues, please contact support with a support ticket to help with the investigation/fix.

authors: jamesnovak tapanm-MSFT

repo: MicrosoftDocs/powerapps-docs


text:
Missing info about appropriate licensing

The Power Apps Admin Portal links to this page when an admin clicks Confirm to convert --> if licensing is not correct it notifies "You can’t convert your trial portal to production as you don’t have an appropriate license.". On this page should be a link to the licensing info page?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7444d166-6678-7ecc-2c33-4c54d4d67ac3
Version Independent ID: a815c5f8-3ab4-d30a-5098-0d865947bdbb
Content: About Power Apps portals lifecycle - PowerApps
Content Source: powerapps-docs/maker/portals/admin/portal-lifecycle.md
Service: powerapps
GitHub Login: @sbmjais
Microsoft Alias: shjais

Thank you for reaching out and your feedback. This feedback is being considered for future updates.


text:
The link to the download page does not work

Hi!
The link from "download Power BI publisher for Excel " does not work (download not available anymore). Can you please have a look at it?
BR

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2fcb95bc-abb8-5147-ddc5-00714e30f79b
Version Independent ID: 45626f2c-9e5c-6bdd-6fbb-b82c279962e0
Content: Analyze in Excel for Power BI - Power BI
Content Source: powerbi-docs/service-analyze-in-excel.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi, @Ghuiles -- thanks for catching that! You're right, the link is broken because Publisher for Excel has been deprecated. Please use Analyze in Excel.
I've removed the link from the article.

authors: Ghuiles maggiesMSFT

repo: MicrosoftDocs/powerbi-docs


text:
Date formats

I must say that I am slightly confused by the date format choices in Power BI. Why is mm/dd/YYYY the standard format, in any part of the software? It is an American date format, that most other people ar unfamiliar with. It is both ambiguous compared to the widely used dd/mm/YYYY date format, but most importantly, it doesn't follow international standard.
The International Organization for Standardization (ISO) has decided, quite some years ago, that the international standard for dates should be YYYY-mm-dd (or YYYYmmdd). This is just as short as the mm/dd/YYYY date format, and has the benefit of being non-ambiguous, but most importantly being the international standard!
Could you please do the entire world a huge favor and change mm/dd/YYYY to YYYY-mm-dd?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4bc558f3-8a74-7154-c048-2dd74ad4eb8a
Version Independent ID: f84aa1a5-4bab-6f6d-a0ba-5040c0f5defb
Content: Use the numeric range slicer in Power BI Desktop - Power BI
Content Source: powerbi-docs/desktop-slicer-numeric-range.md
Service: powerbi
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @ArvidBaa . This looks like product feedback | a product question, rather than documentation feedback. You can submit product feedback or feature ideas by going to https://ideas.powerbi.com. You can also engage with the Power BI engineering team at https://community.powerbi.com.

@mihart you're correct. My mistake.

authors: ArvidBaa mihart


text:
Minor typo

Excellent information. A minor typo in this section.. I think the author may have wanted to say (staging dataflow) and not (stating dataflows)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 76bbffdf-18f6-9001-b75a-57aedc1dcfe0
Version Independent ID: 928761e0-8e55-c01f-9228-7ee5d2971d52
Content: Best practices around designing and developing complex dataflows
Content Source: powerquery-docs/dataflows/best-practices-developing-complex-dataflows.md
Service: powerquery
GitHub Login: @radacad
Microsoft Alias: v-douklo

Hi @pawarbi -
Thanks for your feedback. This typo is fixed.

authors: DougKlopfenstein pawarbi

repo: MicrosoftDocs/powerquery-docs


text:
[BULK UPDATE] DocuTune - Rebranding

Global effort for the Microsoft Learn platform rebrand
The Microsoft team is applying changes to content for the Microsoft Learn platform rebrand. Changes include modifications to current Microsoft Learn and Microsoft Docs terminology as well as associated domain name and content URL path changes.
Please review this draft PR and provide any necessary comments as soon as possible. Because these fixes are tightly scoped, we have approval to automatically merge these changes to the default branch for publication.
This PR was generated via DocuTune. It includes only targeted fixes and minor formatting adjustments.
CorrelationId: d8c4c3ac-d49a-4c95-9ddc-9822ca297907
InitiativeId: docutune-rebranding-2022-09
PointOfContact: Alex Buck

#docutune-draft

Docs Build status updates of commit c41f7bf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

CONTRIBUTING.md
:white_check_mark:Succeeded

project-rome-docs/devicerelay/how-to-guide-for-windows.md
:white_check_mark:Succeeded

project-rome-docs/remote-sessions/how-to-guide-for-windows.md
:white_check_mark:Succeeded

project-rome-docs/user-activities/how-to-guide-for-windows.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

repo: MicrosoftDocs/project-rome


text:
push to live

⚠ NOTE:
This repository only contains automatically generated API documentation, and thus cannot accept pull requests.
If you would like to contribute to the API documentation in this repo, please see the Quantum Development Kit contribution guide to learn more.

Docs Build status updates of commit 3ee91a7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/qsharp/index.md
:warning:Warning
View
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

api/qsharp/index.md

Line 15, Column 54: [Warning-xref-not-found] Cross reference not found: 'microsoft.quantum.libraries.overview'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

repo: MicrosoftDocs/quantum-api


text:
Update ns-winuser-rawkeyboard.md

Add link to a new scan code table. Remove outdated info.

@Karl-Bridge-Microsoft FYI

repo: MicrosoftDocs/sdk-api


text:
Command specific to Ubuntu 16.04, should note that users need to change to 18.04 or 20.04

This command curl https://packages.microsoft.com/config/ubuntu/16.04/prod.list | sudo tee /etc/apt/sources.list.d/msprod.list
Should add a note that if user has a different version of Ubuntu, you may need to change /ubuntu/16.04/ to reflect the applicable version number. For example /ubuntu/18.04/ or /ubuntu/20.04/

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 39bb4ba1-ae62-07a3-f79a-138f14cf2f10
Version Independent ID: beaa4e7d-e771-cc96-0e59-34d9b1d5e8cc
Content: Install SQL Server command-line tools on Linux - SQL Server
Content Source: docs/linux/sql-server-linux-setup-tools.md
Product: sql
Technology: linux
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@alex-jitbit -- Alexander, thank you for your feedback.  I am updating this article.

@alex-jitbit @WilliamAntonRohm - This note is listed in the doc:

@VanMSFT -- Van, should I update that note with "18.04" as well?  It seems clear from the context.

@WilliamAntonRohm - It's implied in the note that the path needs to be changed, but I guess for further clarification, a note update for 18.04 couldn't hurt. Thanks!

authors: VanMSFT WilliamAntonRohm alex-jitbit

repo: MicrosoftDocs/sql-docs


text:
Inconsistent security information on SQL server security

Hi.. there are two Microsoft pages regarding Securing SQL Server.
https://learn.microsoft.com/en-us/sql/relational-databases/security/securing-sql-server?view=sql-server-ver16
https://learn.microsoft.com/en-us/sql/relational-databases/security/sql-server-security-best-practices?view=sql-server-ver16
The "SQL Server security best practices" page talk about some subjects not mentioned in the "securing SQL Server" page.  Which of both pages shall we consider?
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 971e2142-ecc0-357f-2c9f-2f9697a79d3f
Version Independent ID: 971e2142-ecc0-357f-2c9f-2f9697a79d3f
Content: SQL Server security best practices - SQL Server
Content Source: docs/relational-databases/security/sql-server-security-best-practices.md
Service: sql
Sub-service: security
GitHub Login: @dplessMSFT
Microsoft Alias: dpless

@panchovilla1970 -- thank you for your clear feedback and question.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@dplessMSFT -- please look into this issue.

Hi @panchovilla1970. Thanks for your question.
Both articles must be considered.
The first one has a wider scope than the second. In the first one, physical, network, and operating system security is covered. The second goes into specific SQL Server features and configuration options.


text:
Update dynamic-data-masking.md

Current docs state "Four types of masks are available", and then it lists five types (datetime added for sql 2022).

Thanks, @sqlrockstar!


text:
Repo sync for protected CLA branch

The pull request is created from main637859342751541815 to main to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change.

repo: MicrosoftDocs/visualstudio-docs


text:
Please pop a warning before committing when there are no staged changes

It would be very helpful if there was some way to force the git plugin to make you confirm before committing changes, when you haven't staged files.  I run into situations all the time where I tweak some local config file that should not be committed, and then make some changes to other files, and forget to stage the particular files that I want committed, then hit Commit All.  Then I have to go checkout the previous clean version of the mistakenly committed file, and commit again to revert it.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9654b64d-80e5-a28e-30d8-240b02bbe175
Version Independent ID: c4f3eb8e-e203-7452-ba96-b0990107339a
Content: Save your changes with Git commits
Content Source: docs/git/tutorial/commits.md
Product: devops
GitHub Login: @steved0x
Microsoft Alias: sdanie

@ericrrichards Thank you for your feedback. The issues in this repo are for content feedback, and this looks like a product feedback. For product feedback, including feature requests, please file an issue here: https://developercommunity.visualstudio.com/spaces/21/index.html
Thank you.

repo: MicrosoftDocs/vsts-docs


text:
Does the migration still not init git-lfs? How to migrate work boards?

We were just testing this out on a small repository and all of our image binaries seemed to come over just fine (nothing more than a 5MB).  So these are probably not tracked by LFS, but not a problem for our small project we migrated. It'll be a bigger problem with larger projects. Does the Git-tfs tool help with this (I'm not seeing any info on that in the github repo).  Also worried that git-tfs is no longer being maintained. What's the suggested path when we need LFS?
Also there seems to be no mention anywhere of how to migrate an agile workboard from a tfs project to a git project. It would be really helpful to have that info or a tool that just does it.
Thanks!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 44afc4fe-66c8-a745-0037-00748a80beb7
Version Independent ID: 0ea09401-6a08-d745-ff50-7a7b74c41f32
Content: Migrate from TFVC to Git - Azure DevOps
Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/devops-learn-pr?path=%2fdocs%2fgit%2fmigrate-from-tfvc-to-git.md&version=GBlive&_a=contents
Product: devops
Git Login: samgu
Microsoft Alias: routlaw

@Naphier I'm trying to find out for you, I have got a few queries out.
Does the info in this issue apply or help? (Or is there more than one git-tfs?)
https://github.com/git-tfs/git-tfs/issues/1241

@Naphier - If you are just moving your code base from TFVC to Git, there is nothing you need to do to migrate work items. If you are moving your code from TFS to Azure DevOps Services, then you'll want to check out the articles provided here: https://docs.microsoft.com/en-us/azure/devops/articles/migration-overview?view=vsts.

@steved0x That sort of helps, it doesn't make things any easier, though. Migrating TFVC to Git needs to have an option to set up LFS first, really. Even a user prompt that just says "hey we detected a bunch of binaries that might not track well with Git, would you like to track common extensions with Git lfs?" This solution might work out though. We'll have to test to see.
@KathrynEE Are you saying that we can create a git repo under an existing project that's using TFVC? I didn't see that option before, but I am now seeing it. If that's the case then no board migration is needed like you say.
So my only issue would be correctly dealing with LFS.
We've got a couple of weeks before we start migrating so I'll do some research on it too, but sure would be nice to have a tool in Azure DevOps that just handled the large binaries (I know LFS is a bit of a pain).

On further inspection, since we can have the new git repo in the existing Azure Devops project, then I think we're just going to do manual migrations. Most of our repositories are over 1GB anyway, so it seems manual migration is necessary and we can just rely on the TFVC repo's history. We just need to do a freeze and make sure there's nothing we want to revert!

Ya bummer but seems to be the solution. Thanks for the assistance.
On Fri, Dec 14, 2018, 10:24 AM Steve Danielson <notifications@github.com
wrote:

@Naphier https://github.com/Naphier I heard back, if you have a lot of
binaries, then the best solution is to manually migrate the code (ok which
I see is what you have arrived at as well). Then keep the TFVC Repo for
history alongside the new git repo for your current work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/vsts-docs/issues/2676#issuecomment-447357683,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJqcPNiu2WYujqpMYJkC5TtGRylcJIIYks5u48K_gaJpZM4ZHSbP
.

@Naphier Thank you again for your feedback, I'm closing this issue.

authors: KathrynEE Naphier steved0x


text:
Email Notifications

FYI - After you rename a project, Azure DevOps takes the liberty of emailing EVERYONE who has even read access to that project without informing you that it will do so. In our case, while we were POC'ing things we granted everyone in our company read access to a team project and then renamed it which resulted in a blast email to our entire corporation. Not cool!!! I consider this bad behavior on the part of Azure DevOps to send these sorts of blast notifications without informing the user that it will do so.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 03a7de30-26a7-c7ac-2d62-620522bb2f64
Version Independent ID: 35d7c5ce-6ebb-19ff-55e0-fd1fe385f462
Content: Rename a project - Azure DevOps - Azure DevOps
Content Source: docs/organizations/projects/rename-project.md
Product: devops
Technology: devops-accounts
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hi @kpeek, I'm sorry for your frustration and I understand. Team project rename sends emails to everyone in the project if it's under 1,000 users, which I suspect is your case. If you have more than 1,000 users, it sends the email only to PCAs. We haven't heard much from our customers on implementing a "notify project users" button on rename, for example, but I'd suggest submitting a feature request, if you're interested. In the meantime, I'm going to add a warning to the article. I'll let you know once it's been published. Thanks very much for your feedback.

authors: chcomley kpeek


text:
Explain project retention settings

There has been some confusion on how the project-level retention settings work, and we should explain them a bit more thoroughly.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2931f833-b378-efa9-2c43-0d2afea22bd7
Version Independent ID: ba3138ef-dc42-16c9-fcb3-1af441be7eb8
Content: Build and release retention policies - Azure Pipelines
Content Source: docs/pipelines/policies/retention.md
Product: devops
Technology: devops-cicd
GitHub Login: @juliakm
Microsoft Alias: jukullam

@moswald  Thank you for the feedback.
If you don't mind, please include some additional details such as tasks to accomplish, missing info, or confusing sections, and I can assign this to the author.

authors: moswald msebolt