text:
changed wording

in section active/active deployment I changed the term "dialog instances" to "application server"....this is the more correct term in the SAP universe. There are customers who configure an application server in that way, that they only process batch jobs (batch workload) on it. For those the term "dialog instance" may be a bit misleading. The term "application server" is more common!
Thanks for any comments or questions - cheers Frank

@FrankFoese : Thanks for your contribution! The author, @msjuergent, has been notified to review your proposed change.

#sign-off

authors: FrankFoese PRMerger16 msjuergent


text:
Gender neutral language

Change "He'll" to "They'll"

@emberstevens : Thanks for your contribution! The author, @msmimart, has been notified to review your proposed change.

#sign-off

source: gharchive/pull-request

authors: PRMerger14 emberstevens msmimart

repo: MicrosoftDocs/azure-docs

license_type: permissive

license_source: github-api


text:
Updating Red Hat OpenShift docs link in TOC

Pointing to the ARO specific docs, vs generic OKD docs.

@sabbour : Thanks for your contribution! The author, @, has been notified to review your proposed change.


text:
missing dot in the script

also picked up Mark's change for duplicate header cut/paste error

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

#sign-off

authors: JeffGoldner PRmerger


text:
New guide : How to automate stale device management with Graph and Flow

Managed to get this flow working so I documented the steps to recreate it - it'll hopefully be a good intro resource for Graph, Apps, Connectors, and Flow, that applies them to a sysadmin task. When I first found out about Flow I had a really hard time finding something to put it to work on, so it came across as mostly a cool gimmick to play with, but nothing particularly serious. Maybe I'm not the only one that got that sense. This might help dispel that. Plus, the current solution for managing stale devices in AAD manually using the script is kind of clunky, and running it as a scheduled task on a host kind of goes against the promise of the cloud.
I don't expect this to get merged as-is, but I'm not sure how to get what I've got here to something that could be merged, so I figured creating the pull request would start that discussion.
I suspect you also need Azure Premium, at least P1, for this, but wasn't sure how to go about validating that

This is just the second pull request I've made so far and the first new page so I expect there's gonna be some teething trouble, please bear with me lol - hopefully the next time it'll be more in-line with your requirements

The full flow I set up goes further than this, with a 2-phase deletion - first it disables the object at 30 days then it deletes at 60, to give a period of verification. I contemplated covering the whole thing in the guide but since it was already getting long I figured I'd leave that as an obvious exercise to the reader - take what you've learned in the guide to expand the result. I'm not sure which is the better route, so if you have a preference let me know

Should we just close this and forget it?

@ShrCaJesmo: Thank you very much for your contribution! We're having a conversation in-house to figure out the best person to handle this PR. My team works on different tech. Thanks for your patience and for your interest in MS Docs.

All good, I just didn't want to be clogging up PRs if this wasn't interesting, relevant, or useful. Thanks for the response!

#assign:MicrosoftGuyJFlo

Ill take care of this PR. Sent an email to the devices product team for technical review.

#hold-off

Hello,
Just checking in, how's that review with the devices product team going?

Hi @MicrosoftGuyJFlo - Is this PR still in progress? Thanks.

#assign @spunukol

@spunukol Could you provide an update on this PR? Thanks.

@ShrCaJesmo I got a response from the product team today.  If you can email me your contact info I am going to pass that along to them so they can follow up in the future.
From the PM...
Thank you. Automating the flows is something that we have in the product backlog. This looks like a nice way to automate some items.
We are working to enhance the capability of our API’s so that some system objects do not get accidentally deleted. Today this is through the PSH.
Examples are “Auto-pilot” devices.
If there is a way to engage, they can provide a contact and the PM’s can contact them in the future

#please-close

@MicrosoftGuyJFlo I've emailed you, did you receive it?

authors: MicrosoftGuyJFlo ShrCaJesmo cjgronlund ktoliver


text:
Updating "You need to restore a deleted domain"

We changed the amount of days on which customers are allowed to restore an accidentally deleted domain from 7 to 30 days.

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

@cristhianu, Let's discuss this change offline. please send an email to me (Thomas Lin) with the change.
#please-close

authors: PRMerger8 cristhianu genlin


text:
Update request-units.md

Replacing collection with container wherever logically applicable

 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: indcoder sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@mimig1 @SnehaGunda

Duplicate fix to https://github.com/MicrosoftDocs/azure-docs/pull/5489

@indcoder - Thank you for taking the time to make this fix! Someone else contributed a fix just a few minutes before you did, so we're going to merge that PR (5489), but I do appreciate your effort. Thanks!

#please-close

authors: indcoder mimig1 msftclas


text:
Updated claim resolver overview in OAuth2 section

Added refresh_token claim resolver for OAuth2which was missing in the documentation.

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

@yoelhor please confirm

@JasSuri would you have a look?

#sign-off

authors: PRMerger17 SampathDilhan msmimart


text:
Typo "Azure SQL database"→"Azure SQL Database"

https://docs.microsoft.com/en-us/azure/azure-sql/database/maintenance-window-configure?tabs=azure-portal
#PingMSFTDocs

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

Hi @hyoshioka0128. Thanks for your contribution to the documentation.
It looks to me like the text string that's updated in the pull request refers to an instance of the Azure service, in which case it should remain lowercase. We'll close this pull request. Thank you.


text:
Update AD DS documentation - manual steps

I added to this docs after having issues decoding the steps myself. These new and more elaborating steps have been tested in a production environment, and is verified to work.

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

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

@khdownie
Thanks for reviewing the proposed changes. 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"

Anything else I need to add to this approach, or are we good to merge?

@erlandsen-tech you won't be able to merge this because the original file has changed, and you'll get merge conflicts. Also, we definitely don't want to replace the simpler Windows-only approach, because most of our users are Windows users. We could add your code in a separate section for non-Windows users; however, AD auth for Linux is only recently supported and we're developing a separate doc on that.

@erlandsen-tech submitted this to Linux team for testing and consideration. OpenLDAP is a viable auth method, but we only publish tested methodologies.

#please-close


text:
Updated the Billing model.

Changed the billing mention of [core] to [Physical Core]

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

repo: MicrosoftDocs/azure-stack-docs


text:
fix missing descriptions - batch 5

@MandiOhlinger @MightyPen batch 5 of missing desc fixes

Docs Build status updates of commit b73087b:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit b73087b:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

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

File
Status
Preview URL
Details

biztalk/core/smtp-adapter-property-schema-and-properties.md
:warning:Warning
View
Details

biztalk/core/soap-adapter-property-schema-and-properties.md
:warning:Warning
View
Details

biztalk/core/soap-headers-with-consumed-wcf-services.md
:warning:Warning
View
Details

biztalk/core/soap-headers-with-published-wcf-services.md
:warning:Warning
View
Details

biztalk/core/specifying-soap-actions-for-wcf-send-adapters.md
:warning:Warning
View
Details

biztalk/core/specifying-the-message-body-for-the-wcf-adapters.md
:warning:Warning
View
Details

biztalk/core/step-10-configure-the-x12-and-as2-trading-partner-agreement.md
:warning:Warning
View
Details

biztalk/core/step-7-configure-a-send-port-to-send-the-acknowledgment-to-trading-partner.md
:warning:Warning
View
Details

biztalk/core/step-8-configure-the-trading-partner-agreement-between-the-parties.md
:warning:Warning
View
Details

biztalk/core/supported-windows-sharepoint-services-column-types.md
:warning:Warning
View
Details

biztalk/core/using-soap-headers-in-orchestrations.md
:warning:Warning
View
Details

biztalk/core/using-soap-headers-in-wcf-messages-with-pipeline-components.md
:warning:Warning
View
Details

biztalk/core/segment-exceeds-maximum-use-description.md
:bulb:Suggestion
View
Details

biztalk/core/segment-has-data-element-errors.md
:bulb:Suggestion
View
Details

biztalk/core/segment-has-trailing-delimiter-s-at-component-or-sub-component-level.md
:bulb:Suggestion
View
Details

biztalk/core/segment-not-in-defined-transaction-set.md
:bulb:Suggestion
View
Details

biztalk/core/segment-not-in-proper-sequence.md
:bulb:Suggestion
View
Details

biztalk/core/segment-repeats-less-than-the-minimum-allowed-number-of-times.md
:bulb:Suggestion
View
Details

biztalk/core/segment-should-have-a-name-with-at-least-two-characters.md
:bulb:Suggestion
View
Details

biztalk/core/send-errors.md
:bulb:Suggestion
View
Details

biztalk/core/service-instance-states.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10500.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10501.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10502.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10503.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10504.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10505.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10506.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10507.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10508.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10509.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10510.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10511.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10512.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10513.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10514.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10515.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10516.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10517.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10518.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10519.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10520.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10521.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10522.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10523.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10524.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10525.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10526.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10527.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10528.md
:bulb:Suggestion
View
Details

This comment lists only the first 50 files in the pull request.

biztalk/core/smtp-adapter-property-schema-and-properties.md

Line 43, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/smtp-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/soap-adapter-property-schema-and-properties.md

Line 45, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/soap-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/soap-headers-with-consumed-wcf-services.md

Line 25, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/soap-headers-with-published-wcf-services.md

Line 23, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 45, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties/Promote' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 49, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties/WriteToContext' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/specifying-soap-actions-for-wcf-send-adapters.md

Line 44, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/system-properties#Operation' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 48, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/system-properties#Operation' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/specifying-the-message-body-for-the-wcf-adapters.md

Line 183, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com/schemas/bts2010' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 207, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com/schemas/bts2010' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 237, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com/schemas/bts2010' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/step-10-configure-the-x12-and-as2-trading-partner-agreement.md

Line 125, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/step-7-configure-a-send-port-to-send-the-acknowledgment-to-trading-partner.md

Line 64, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/Edi/X12#X12_997_Root' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/step-8-configure-the-trading-partner-agreement-between-the-parties.md

Line 78, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 108, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/Edi/X12' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/supported-windows-sharepoint-services-column-types.md

Line 41, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/using-soap-headers-in-orchestrations.md

Line 30, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/SOAPHeader' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 33, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/SOAPHeader' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/using-soap-headers-in-wcf-messages-with-pipeline-components.md

Line 24, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/segment-exceeds-maximum-use-description.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-has-data-element-errors.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-has-trailing-delimiter-s-at-component-or-sub-component-level.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-not-in-defined-transaction-set.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-not-in-proper-sequence.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-repeats-less-than-the-minimum-allowed-number-of-times.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-should-have-a-name-with-at-least-two-characters.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/send-errors.md

Line 23, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 43, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/service-instance-states.md

Line 90, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 108, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10500.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10501.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10502.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10503.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10504.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10505.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10506.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10507.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10508.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10509.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10510.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10511.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10512.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10513.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10514.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10515.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10516.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10517.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10518.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10519.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10520.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10521.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10522.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10523.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10524.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10525.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10526.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10527.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10528.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

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 b73087b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/core/smtp-adapter-property-schema-and-properties.md
:warning:Warning
View
Details

biztalk/core/soap-adapter-property-schema-and-properties.md
:warning:Warning
View
Details

biztalk/core/soap-headers-with-consumed-wcf-services.md
:warning:Warning
View
Details

biztalk/core/soap-headers-with-published-wcf-services.md
:warning:Warning
View
Details

biztalk/core/specifying-soap-actions-for-wcf-send-adapters.md
:warning:Warning
View
Details

biztalk/core/specifying-the-message-body-for-the-wcf-adapters.md
:warning:Warning
View
Details

biztalk/core/step-10-configure-the-x12-and-as2-trading-partner-agreement.md
:warning:Warning
View
Details

biztalk/core/step-7-configure-a-send-port-to-send-the-acknowledgment-to-trading-partner.md
:warning:Warning
View
Details

biztalk/core/step-8-configure-the-trading-partner-agreement-between-the-parties.md
:warning:Warning
View
Details

biztalk/core/supported-windows-sharepoint-services-column-types.md
:warning:Warning
View
Details

biztalk/core/using-soap-headers-in-orchestrations.md
:warning:Warning
View
Details

biztalk/core/using-soap-headers-in-wcf-messages-with-pipeline-components.md
:warning:Warning
View
Details

biztalk/core/segment-exceeds-maximum-use-description.md
:bulb:Suggestion
View
Details

biztalk/core/segment-has-data-element-errors.md
:bulb:Suggestion
View
Details

biztalk/core/segment-has-trailing-delimiter-s-at-component-or-sub-component-level.md
:bulb:Suggestion
View
Details

biztalk/core/segment-not-in-defined-transaction-set.md
:bulb:Suggestion
View
Details

biztalk/core/segment-not-in-proper-sequence.md
:bulb:Suggestion
View
Details

biztalk/core/segment-repeats-less-than-the-minimum-allowed-number-of-times.md
:bulb:Suggestion
View
Details

biztalk/core/segment-should-have-a-name-with-at-least-two-characters.md
:bulb:Suggestion
View
Details

biztalk/core/send-errors.md
:bulb:Suggestion
View
Details

biztalk/core/service-instance-states.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10500.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10501.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10502.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10503.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10504.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10505.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10506.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10507.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10508.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10509.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10510.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10511.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10512.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10513.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10514.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10515.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10516.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10517.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10518.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10519.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10520.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10521.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10522.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10523.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10524.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10525.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10526.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10527.md
:bulb:Suggestion
View
Details

biztalk/core/single-sign-on-event-10528.md
:bulb:Suggestion
View
Details

This comment lists only the first 50 files in the pull request.

biztalk/core/smtp-adapter-property-schema-and-properties.md

Line 43, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/smtp-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/soap-adapter-property-schema-and-properties.md

Line 45, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/soap-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/soap-headers-with-consumed-wcf-services.md

Line 25, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/soap-headers-with-published-wcf-services.md

Line 23, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 45, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties/Promote' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 49, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties/WriteToContext' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/specifying-soap-actions-for-wcf-send-adapters.md

Line 44, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/system-properties#Operation' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 48, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/system-properties#Operation' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/specifying-the-message-body-for-the-wcf-adapters.md

Line 183, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com/schemas/bts2010' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 207, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com/schemas/bts2010' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 237, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com/schemas/bts2010' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/step-10-configure-the-x12-and-as2-trading-partner-agreement.md

Line 125, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/step-7-configure-a-send-port-to-send-the-acknowledgment-to-trading-partner.md

Line 64, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/Edi/X12#X12_997_Root' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/step-8-configure-the-trading-partner-agreement-between-the-parties.md

Line 78, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/EDI/X12/2006' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 108, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/Edi/X12' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/supported-windows-sharepoint-services-column-types.md

Line 41, Column 1: [Warning-insecure-link] Link 'http://www.microsoft.com' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/using-soap-headers-in-orchestrations.md

Line 30, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/SOAPHeader' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 33, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2003/SOAPHeader' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/using-soap-headers-in-wcf-messages-with-pipeline-components.md

Line 24, Column 1: [Warning-insecure-link] Link 'http://schemas.microsoft.com/BizTalk/2006/01/Adapters/WCF-properties' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.

biztalk/core/segment-exceeds-maximum-use-description.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-has-data-element-errors.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-has-trailing-delimiter-s-at-component-or-sub-component-level.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-not-in-defined-transaction-set.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-not-in-proper-sequence.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-repeats-less-than-the-minimum-allowed-number-of-times.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/segment-should-have-a-name-with-at-least-two-characters.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/send-errors.md

Line 23, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 43, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/service-instance-states.md

Line 90, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 108, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10500.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10501.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10502.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10503.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10504.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10505.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10506.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10507.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10508.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10509.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10510.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10511.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10512.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10513.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10514.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10515.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10516.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10517.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10518.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10519.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10520.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10521.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10522.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10523.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10524.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10525.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10526.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10527.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

biztalk/core/single-sign-on-event-10528.md

Line 21, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

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

repo: MicrosoftDocs/biztalk-docs


text:
Added ConsoleConnector language and example

Building console bots are a quick and easy way to get up-and-running, but the examples from the old docs are not in the new docs. I think adding some code examples and language back in is appropriate. Even though most will want to use the ChatConnector because of the Bot Framework channels, console bots and the ConsoleConnector serve a good purpose for prototyping, and as potential set-up utilities on devices without (or with limited) access to the Internet.

@szul,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

authors: msftclas szul

repo: MicrosoftDocs/bot-framework-docs


text:
Adding another profile

Accepting and added Frank

OPS Build status updates of commit 421e73b:
:clock10: Preparing: average preparing time is 40 sec(s)

OPS Build status updates of commit 421e73b:
:clock10: Incremental building: average incremental building time is 36 sec(s)

OPS Build status updates of commit 421e73b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/frank-boucher.yml
:white_check_mark:Succeeded
View

advocates/index.html.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/frank-boucher.png
:white_check_mark:Succeeded
View

advocates/toc.yml
: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/cloud-developer-advocates


text:
Step 9 has mistake

In Step 9, of 'Implement a Trigger', it says to put the manifest file under the folder 'POSAPIExtension '.  Whereas I believe it should say to put it under the folder 'SuspendReceiptSample'.  My guess is this was a copy and paste error.
Also, is this the correct place to make corrections to the articles?  And/or where can I contribute articles myself?

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

ID: 205c9cdc-7229-ed08-63d2-166f7f9d7416
Version Independent ID: 5f7574c0-e12f-785d-e7d9-0efbe67e5fec
Content: Retail Modern POS (MPOS) triggers and printing - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/retail/dev-itpro/pos-trigger-printing.md
Service: dynamics-365-retail
GitHub Login: @mugunthanm
Microsoft Alias: mumani

@blackjoker17,  Thanks for pointing this out. To update the content directly, click "Edit" in the upper right corner of any of our Docs.microsoft.com topics, make your changes and then propose the change. We'll review the change and publish it after it passes internal review. For more information about contributing, see our Contributor's guide.
Definitely keep entering issues for when you see a gap in the documentation or you find a mistake in the documentation that you don't want to fix yourself by editing the topic.

Bug logged for investigation: 237905

This topic has been fixed and will be published by the end of this week.

source: gharchive/issue


text:
Misc typo

Hello,
The example code contains a compile error. The line
Options := Text000 should be terminated with a semicolon e.g.
Options := Text000;. Does anyone actually compile the sample code that is used in the docs?
[Enter feedback here]

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

ID: b920058d-dbd2-5b27-9ee5-24ebf643449d
Version Independent ID: 1614985d-8fcd-31cd-b8cc-ce45dac35774
Content: StrMenu Method - Business Central
Content Source: dev-itpro/developer/methods-auto/dialog/dialog-strmenu-method.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Hello, Thanks for the feedback, and sorry for the inconvenience. It has been fixed and an update will be published soon. We do try to compile all examples, but we sometimes miss things. Thanks.

authors: gary-PSSI jswymer


text:
BC runtime version compatibility

"A project can be published to the server with an earlier or with the same runtime version as the server" is wrong
It should be
"A project can be published to the server with an newer or with the same runtime version as the server"

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

ID: 1bac24fa-c9eb-695a-bdd5-3dbe4109a0dc
Version Independent ID: a09fc47a-123f-a136-d4e5-e986dfc94522
Content: Choosing Runtime Version in AL - Business Central
Content Source: dev-itpro/developer/devenv-choosing-runtime.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for the feedback, we're rewording the sentence to avoid any misunderstandings. Will be fixed with the next doc refresh.

authors: SusanneWindfeldPedersen quocdunginfo


text:
Lies, all lies!

It uses way too much CPU and RAM (despite of what you are claiming, and you claim whatever you want, that does not make your statements true) and it is launched many, many times for just one instance of Teams.
It is not allowed to run on my systems anymore, so I will have to use the web version of Teams, because you effers do not know how to write good software and need to use even worse garbage, just because it is from the same company (which has known for their garbage since they got a bit more known).

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

ID: a98f4d73-3a87-7836-be1e-d98cf264768c
Version Independent ID: a98f4d73-3a87-7836-be1e-d98cf264768c
Content: WebView2 end-user FAQ - Microsoft Edge Developer documentation
Content Source: microsoft-edge/webview2/concepts/end-user-faq.md
Service: microsoft-edge
Sub-service: webview
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

If you have specific technical feedback about WebView2, I would encourage you to provide it, in a civil and respectful way, with additional details, to the WebView2 team at https://github.com/MicrosoftEdge/WebView2Feedback/issues/new.
I will now close this issue as:

out of scope for this repository
violating the Microsoft open source code of conduct.

repo: MicrosoftDocs/edge-developer


text:
CoreWebView2 is null and doesn't load content in WPF window

Installed nuget package

<wv2:WebView2 Name="webView"
Source="https://www.microsoft.com" />
Any workaround for this?

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

ID: ba9dc9d2-795c-9612-3585-408b4621c080
Version Independent ID: f73fc16d-d842-4507-9fdb-b42856720355
Content: Microsoft Edge WebView 2 for WPF apps - Microsoft Edge Development
Content Source: microsoft-edge/webview2/gettingstarted/wpf.md
Product: microsoft-edge
Technology: webview
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

I am facing similar issues - BTW first, the documented sample code has an extra closing tag in there that had to be remove.   After removing the extra closing tag, solution builds, window pops up on debug but website not loading.

I'm having the same issue. CoreWebView2 is null when trying to navigate to any URL. Hardcoded Source doesn't load either.

could it be already captured in this bug?
https://github.com/MicrosoftEdge/WebViewFeedback/issues/179

What is the fix for this? Are the hints from here work for you guys?MicrosoftEdge/WebViewFeedback#179

@dk511 Haven't tried yet. This is more a workaround than anything. So I will be waiting for a stable release as I have a bit of time for now.

I was able to get the Getting Started app to work after installing the Canary version of edge -
which can be found here - https://www.microsoftedgeinsider.com/en-us/download

Looks like the issue was resolved. I'll go ahead and close out this issue now. Thanks.

@dk511 is this fixed for you? I created a new VSIX project in VS 2017, unchecked "Sign the assembly" in the project (https://github.com/MicrosoftEdge/WebViewFeedback/issues/181), added a tool window, and included the WebView2 as per https://docs.microsoft.com/en-us/microsoft-edge/webview2/gettingstarted/wpf, but just see a gray box in the tool window.
Calling methods like Reload() on the WebView2 results in an exception:
'Attempted to use WebView2 functionality which requires its CoreWebView2 prior to the CoreWebView2 being initialized.  Call EnsureCoreWebView2Async or set the Source property first.'

Doesn't look like this is resolved https://github.com/MicrosoftEdge/WebViewFeedback/issues/195#issuecomment-645066820

authors: BastienEscaich Reezaali chrisluna dk511 priyasgs


text:
What's New 94

The rendered article for review:
https://review.docs.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools?branch=pr-en-us-1424
In the course of setting up a screenshot for What's New (the Extension item), I also updated and clarified and added screenshots in this subsection of the Edge DevTools Extension article:
https://review.docs.microsoft.com/en-us/microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension?branch=pr-en-us-1424#changing-the-extension-settings
and the subsection below it.

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

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-elements.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-new-tab.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9f70cb9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-elements.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-new-tab.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-elements.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-new-tab.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3d08349:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/edge-tools-open-settings-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/view-changelog-menuitem.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8e2cfe7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/console/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/edge-tools-open-settings-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/view-changelog-menuitem.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/console/console-debug-javascript.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/console/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/edge-tools-open-settings-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/view-changelog-menuitem.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5d40f42:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/console/console-debug-javascript.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/console/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/07/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/edge-tools-open-settings-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/view-changelog-menuitem.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@erdraud @zoherghadyali
After some Teams chat that modified this PR's review comments, I only made the following slight changes re: this feature:

In devtools.md (= What's New), changed "error string" or "error message" to "error".  Changed the heading from:
Look up error messages on the web from the Console
to:
Search for Console errors on the web
In console.index.md, the heading remains as:
Look up error messages on the web from the Console
It's a requirement that the equivalent sections be non-identical in the What's New vs. Console overview articles.

In console/index.md and console/debug-javascript.md, changed "error string" to "error message".

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

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/console/console-debug-javascript.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/console/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/07/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/edge-tools-open-settings-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/view-changelog-menuitem.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/console/console-debug-javascript.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/console/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/07/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/edge-tools-open-settings-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/view-changelog-menuitem.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 7ac9560:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/console/console-debug-javascript.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/console/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/07/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/edge-tools-open-settings-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/view-changelog-menuitem.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/console/console-debug-javascript.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/console/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/css/css-in-js.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/07/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2021/09/devtools.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/breakpoint-icons-displayed-in-vs-code-themes.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-dark-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/devtools-extension-light-theme.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/nav-to-more-tools-button-with-keyboard.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/media/2021/09/search-console-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/edge-tools-open-settings-icon.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/media/view-changelog-menuitem.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel


text:
Focus Mode screenshot updates for the Console DOM interactions article.

This PR updates all screenshots in the microsoft-edge/devtools-guide-chromium/console/console-dom-interaction.md docs to match the new Focus Mode design.
I also reworked some of the content to match the simpler demo page I used. I didn't want to use the DMC page as demo as we know this often changes and may lead to bugs in our docs.

Docs Build status updates of commit 9db3c31:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/console/console-dom-interaction.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-add-border.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-change-content.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-complex-css-selector.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-copy-js-path.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-filter-link-data.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-filter-out-empty-links.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-get-all-links.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-get-form-events.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-get-generated-headings.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-get-reference.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-highlight-documentation.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-highlight-element.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-highlight-links.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-monitor-events.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-monitor-key-events.msft.png
:white_check_mark:Succeeded

microsoft-edge/devtools-guide-chromium/media/console-dom-overflow-menu-in-elements.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-too-much-link-information.msft.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/media/console-dom-use-inspector-to-get-element.msft.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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel


text:
a typo

🛑 IMPORTANT: You can get your feedback addressed faster if you use the comment section for the article in which you encountered a problem.
Link to article:
https://docs.microsoft.com/en-us/power-bi/guided-learning/visualizations?tutorial-step=16
Problem:
a typo: "You can change how Powwer BI summarizes the data...."  right before the second screenshot of the bottom

This article no longer exists. Closing.

authors: mairaw sophiexu

repo: MicrosoftDocs/feedback


text:
Broken Table

[Broken Table]
"https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-020"

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Duplicate #3230 .
Closed #3231 .


text:
[VS Code] Joining collaboration session: Live Share was unable to start the agent fast enough. Reload to try again

Error:
Joining collaboration session: Live Share was unable to start the agent fast enough. Reload to try again
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
1.0.45

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.33.1

platformName
Windows

platformVersion
10.0.16299

Thanks for submitting this issue, @subashini08.
Your logs may provide us with helpful information. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.

I'm closing this issue due to inactivity and lack of information. If you hit this problem again, please feel free to reopen.

repo: MicrosoftDocs/live-share


text:
Versão corrompida

Issue Type: Bug
Já instalei e desistalei varias vezes e sempre aparece a mensagem de corrompido
Extension version: 1.0.2236
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz (4 x 3292)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.92GB (1.98GB free)

Process Argv

Screen Reader
no

VM
0%

Hi, thank you for reaching out. Would you try the following and let us know if it unblocks you ? -> Ctrl + Shift + P - brings the Command Palette. Then you can start typing Live Share : Repair Installation

Also, your logs may provide us with helpful information. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.

linking with #180

Mesmo fazendo o indicado, continua dando erro

Além disso, seus registros podem nos fornecer informações úteis. Você pode acessá-los através do Live Share: Export Logscomando na paleta de comandos ( ctrl + shift + p) e anexá-los a esse problema.

live_share.zip

thank you for attaching your logs. We track the issue in #3346 . I will close this issue as duplicate. Please follow #3346 , we will let you there, when we have a fix for this issue.

authors: naaracrv setaskin


text:
Possibility to customize M365 Group expiration policy Email content and logo

Microsoft-365-groups-expiration-policy is fantastic feature . Is it possible to customize the email which is sent part of expiration ?. We have a need to add additional information inside email which is sent. Also possibility to add logo would be helpful.

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

ID: 979f0a6e-be32-af1e-5724-d1104ebe3ef5
Version Independent ID: cb9b993a-2224-5bb8-64b8-d1afa7a71c8e
Content: Microsoft 365 group expiration policy
Content Source: microsoft-365/solutions/microsoft-365-groups-expiration-policy.md
Service: o365-administration
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@gurubn Thank you for your feedback. While I don't think this is possible, I'll test this and provide you an update.
Thanks
Sri

@gurubn Thank you for your feedback. This is currently not possible and we have a UserVoice open for this -https://office365.uservoice.com/forums/286611-microsoft-365-groups/suggestions/20487847-customize-group-expiration-email and the product group is already looking at a few options to see how we can solve this problem.
@yogkumgit There are no changes in the document. This issue can be closed.
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @gurubn Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

authors: gurubn msbemba yogkumgit


text:
Support Article gives steps for classic admin exchange site but links to new one

These steps are for the classic admin exchange, but the link is to the new admin exchange.  Plus, there doesn't appear to be a way to set this up in the new admin exchange.  If there is, please update steps accordingly.  Thank you.

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

ID: b725ac58-0fa5-9f7d-84fa-a8541477fe0e
Version Independent ID: f2acd0d0-60b8-0744-e241-06fb753aa5d1
Content: Allow members to send as or send on behalf of a group
Content Source: microsoft-365/solutions/allow-members-to-send-as-or-send-on-behalf-of-group.md
Service: o365-administration
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@avnermiz Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/7927
Once the author approves, the changes will be live.
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @avnermiz 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.

Happy to help.  Thanks for updating so quickly!

authors: avnermiz msbemba yogkumgit


text:
Update manage-auto-investigation.md

updated wordings for terms of auto remediation
Fixes https://github.com/MicrosoftDocs/microsoft-365-docs/issues/12434

@JohanFreelancer9 Please copy review


text:
Added missing space

A space is missing between "he" and "she".

Hi Jim,
This typo is now corrected.
Thanks!
Maite
From: Jim Liu @.>
Sent: Wednesday, March 24, 2021 9:12 AM
To: MicrosoftDocs/microsoft-style-guide @.>
Cc: Subscribed @.***>
Subject: [MicrosoftDocs/microsoft-style-guide] Added missing space (#219)
A space is missing between "he" and "she".

You can view, comment on, or merge this pull request online at:
https://github.com/MicrosoftDocs/microsoft-style-guide/pull/219https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137856965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=hd4DKN%2BpivZOswfLNirZDAptiReiKiR2R6RP%2Beha86w%3D&reserved=0
Commit Summary

Added missing space

File Changes

M styleguide/grammar/nouns-pronouns.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219%2Ffiles%23diff-7bcd8fd4f8d61b78586ff29deddefb44dd3406ba32a5ca07e80a491b79045f5a&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137856965|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=7DL2gQTa4n%2BsSMSt6MN2rdl%2BEUKIkAA1wZY58sYP%2FUE%3D&reserved=0 (2)

Patch Links:

https://github.com/MicrosoftDocs/microsoft-style-guide/pull/219.patchhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219.patch&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137866930|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=tmTaEwo78456cfOTz7eK%2BntTN3kNWAbgqSW%2FBMMu6Uk%3D&reserved=0
https://github.com/MicrosoftDocs/microsoft-style-guide/pull/219.diffhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219.diff&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137866930|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dbNgyQf1ntkK%2B4vfoc9wbEb09cTLZCVo8IbznHHZ0gs%3D&reserved=0

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-style-guide%2Fpull%2F219&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137876883|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qHDGfJ31m8tdAP%2B87w1melRD5KqsCPImI25u21ux2pU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASXUAR27RF5ZPCA6Y3KII3TTFGNEHANCNFSM4ZWX2BFA&data=04|01|v-maites%40microsoft.com|5fc3f306638249b827d408d8ee9c78a5|72f988bf86f141af91ab2d7cd011db47|1|0|637521703137876883|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=O%2B3XFkkuuA0KuPwa2Z1DB2wKYUXvAK8%2Fad8QYG%2F76eE%3D&reserved=0.

authors: jim-liu maitesadaba

repo: MicrosoftDocs/microsoft-style-guide


text:
Fix broken link in Update email-troubleshooting-guide.md (#350)

Update email-troubleshooting-guide.md

Docs Build status updates of commit 8a48363:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/installation/email-troubleshooting-guide.md
: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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel

repo: MicrosoftDocs/msftdynamicsgpdocs


text:
Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree


text:
Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 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: ArghaKBera sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

authors: ArghaKBera msftclas


text:
gulp installation

The suggested installation command for gulp "npm install gulp" didn't work for me. Instead, I've used "npm install --globald gulp-cli"

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

ID: c4fa27cb-544f-f8a2-97a7-4b31528c1b80
Version Independent ID: fa69cd6f-1ef4-706d-2816-aa709714b0aa
Content: Get started with App Studio and Node.js - Teams
Content Source: msteams-platform/tutorials/get-started-nodejs-app-studio.md
Product: msteams
GitHub Login: @clearab
Microsoft Alias: anclear

"npm install gulp" doesn't work sometimes because of version conflicts.
We need to use "rm --global gulp" to clear out any version conflicts and then run "npm install --global gulp-cli".

authors: Subhasish-msft georgschwienbacher

repo: MicrosoftDocs/msteams-docs


text:
[Design][Linkupdate][1474642]

Link updated

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

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
: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

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

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
: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:
bad notes at the top (related to #1883)

this article says "IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy." yet the article on the other cmdlet has the exact opposite message at the top.

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

ID: b37f6ef0-492a-abe8-77b9-c8ba9f4d52fb
Version Independent ID: a2455db6-096b-aca1-3dc1-031fec4f3bb2
Content: Get-CsTeamsInteropPolicy (skype)
Content Source: skype/skype-ps/skype/Get-CsTeamsInteropPolicy.md
Service: skypeforbusiness-powershell
GitHub Login: @kenwith
Microsoft Alias: kenwith

One says that TeamsInteropPolicy has been replaced by TeamsUpgradePolicy, the other says that TeamsUpgradePolicy has replaced TeamsInteropPolicy.  The been is the key message here.

aha ok, you're right. This is distracting wording however. I would expect to see the note at the top of the legacy article and nothing to distract the reader if they've landed on the current article/method.

@Mike-Crowley Thank you for this feedback
I'll get this information over to the PowerShell team so we can get these to articles investigated. I'm going to also make this comment on the other issue that you have as well.
The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

PR:
https://github.com/MicrosoftDocs/office-docs-powershell/pull/2767

authors: AndreaBarr Mike-Crowley dariomws306 islubin

repo: MicrosoftDocs/office-docs-powershell


text:
Update recipientfilter-properties.md

Fixed link.

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

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md
:white_check_mark:Succeeded
View (exchange-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.

Docs Build status updates of commit 1bd8c44:
:clock10: Full build: the average full build time is 11 min(s) 51 sec(s), this is based on the last 999 build(s) for this repository.

Docs Build status updates of commit 1bd8c44:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md
:white_check_mark:Succeeded
View (exchange-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:
How should AADHOST variable be setup for the ALM accelerator deployment pipeline

In the deploy pipelines it runs the commands in set-spn-token.yml which calls the powershell script dataverse-webapi-functions.ps1.
This has a dependency on a variable being set somewhere for AADHOST.  I cant see anywhere in the documentation where it says where this should be setup.
I was able to workaround this problem by adding a variable to the alm-accelerator-variable-group with a name of AADHOST and a value of login.microsoftonline.com
My set-spn-token step then works ok
Is this a step missing in the documentation on the below page section
https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-almacceleratorpowerplatform#create-pipeline-global-variables

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

ID: 5d58c244-3aaa-48e6-8b6d-205521a0bc52
Version Independent ID: 5d58c244-3aaa-48e6-8b6d-205521a0bc52
Content: Set up ALM accelerator for Microsoft Power Platform components manually - Power Platform
Content Source: power-platform/guidance/coe/setup-almacceleratorpowerplatform.md
Service: power-platform
Sub-service: guidance
GitHub Login: @mikefactorial
Microsoft Alias: v-mikeochs

@michaelstephensonuk what you have done is the correct course of action. We have an issue in the coe-starter-kit repo to address this issue in the April release. https://github.com/microsoft/coe-starter-kit/issues/1940. Closing this out for now. Feel free to add anything additional to the coe-starter-kit issue.

Reopening until fixed in April release

authors: michaelstephensonuk mikefactorial

repo: MicrosoftDocs/power-platform


text:
Error Opening File

After importing Powerapps, when trying to edit the app, I am getting the error saying "This application xx could not be found in the tenant"
Similar to the ticket opened before.

Is this in regard to some Microsoft docs article? Please provide its URL. Is this a developer,admin, or end-user question? Thanks

Is this in regard to some Microsoft docs article? Please provide its URL. Is this a developer,admin, or end-user question? Thanks

Thanks for contacting us. As we haven’t heard back from you, I am closing this issue. If you need further help, please reopen the issue or open a new issue.

authors: Nkrb bibinbastian

repo: MicrosoftDocs/powerapps-docs


text:
[BUG] Canvas size wrong

Hi!
when I set the size to 100 * 100 it's displayed in 320 * 320 px.

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

ID: 8ba2ea78-be6e-2715-7e7d-a18d6a628c86
Version Independent ID: e9bb4980-2e68-4921-d13c-729e48f03ad3
Content: Customize the screen size and orientation of a canvas app embedded on a model-driven form - Power Apps
Content Source: powerapps-docs/maker/model-driven-apps/embedded-canvas-app-customize-screen.md
Service: powerapps
GitHub Login: @aneesmsft
Microsoft Alias: matp

@DEV-PBO-DEV - Thanks for contacting us. It appears you are experiencing a possible bug with the feature and not with the documentation. We're unable to handle Support requests for the product here. To contact Support, see here: https://powerapps.microsoft.com/support/
Closing this issue.