text:
Storage Class for Allways on

@Cedric-Bravo commented on Mon Jul 01 2019
Hi,
I'm surprised to see RA-GRS blob storage for the cross AZ scenario.
Did you want to mention ZRS ?

Détails du document
⚠ Ne pas modifier cette section. C’est obligatoire pour docs.microsoft.com ➟ Liaison des problèmes GitHub.

ID: 15036ef6-9c0b-044e-d600-b9f90f039720
Version Independent ID: 6fe5cd14-a1ad-e183-a048-d72686abb969
Content: Haute disponibilité : service Azure SQL Database
Content Source: articles/sql-database/sql-database-high-availability.md
Service: sql-database
Sub-service: high-availability
GitHub Login: @jovanpop-msft
Microsoft Alias: sashan

Hi team,
I'm moving this here because the contributor's comment is refering the original documentation
kind regards

Thank you for bringing this to our attention. Depending on the service tier your Azure SQL Database is deployed, Basic, Standard, and General Purpose service tier leverage LRS (Locally Redundant Storage) as there is no Geo-Replication occurring (See Image). With Premium and Business Critical service tiers where geo-replication is part of the service, the underlying storage is RA-GRS (Read Access - Geo-Redundant Storage)(See Image).
The use of ZRS (Zone Redendant Storage) is not applicable as ZRS does not support Read Access in the case of an outage. Please see additional details fos the differant Azure Storage options (link).

Hi thanks a lot for the reply,
I still don't understand why you need "Read Access - Geo-Redundant Storage" for Allways on cluster since the cluster nodes need RW access to storage and the cluster operate into the same region (and RA-GRS is region replication).
Why did you configure Region replication ? There is no node to read the data since they are into the same region ? image here

Ok, i think got it... the RA-GRS is for backup file not database and log !
In prenium and Business critical service tiers, database file are stored in local SSD.
Correct ?
(The article is a bit confusing, maybe need to place the database file on the schema)

Actually, the database files are mirrored between the local SSDs and the associated storage account (LRS or RA-GRS). The difference between the two is if the region your instance is deployed to was to go off-line, with LRS your entire solution will become unavailable. With RA-GRS, the mirror activity will allow you to access the data in one of the paired regions established during initial set-up.
With LSR, the local SSDs act more like a cache and the .ldf and .mdf files are hosted in the Azure Storage account, all in the same region. With RA-GRS, because you have secondaries in different regions, these secondaries have exact copies of the .ldf/.mdf that are hosted on each respective set of SSDs in those paired regions (via the Always ON AG), and the RA-GRS storage provides a paired host for the backup files to be written to. The result is that regardless of the disaster scenario, there will always be the availability of your data.
Please let me know if you have any additional questions.

Thanks mike,
So in this scenario, what happen to my running database in case of a complete region outage ?
Does the database is still running ? (not only a backup availability).?

@Cedric-Bravo With Basic, Standard, and General Purpose deployments and LRS storage, if the region was to experience a complete outage your entire instance becomes unavailable. With Premium and Business Critical deployments and RA-GRS storage, your solution may experience a minor (less than 20 seconds) service interruption if the region your primary instance was to experience a complete outage., as one of the secondaries will become the primary and service continues as normal. Does this make sense?

Ye mike, i understand that Premium and Business Critical deployments protect me from a region black out (minus a failover delay). This is not what is explain in the article that mention only a HA across AZ into the same region, not HA across Region. Does the article is outdated ?

By default, the cluster of nodes for the premium availability model is created in the same datacenter. With the introduction of Azure Availability Zones, SQL Database can place different replicas in the cluster to different availability zones in the same region. To eliminate a single point of failure, the control ring is also duplicated across multiple zones as three gateway rings (GW). The routing to a specific gateway ring is controlled by Azure Traffic Manager (ATM). Because the zone redundant configuration in the Premium or Business Critical service tiers does not create additional database redundancy, you can enable it at no extra cost. By selecting a zone redundant configuration, you can make your Premium or Business Critical databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. You can also convert any existing Premium or Business Critical databases or pools to the zone redundant configuration.

Thanks for the additional feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@jovanpop-msft @CarlRabeler Customer has pointed out a detail that likely needs some clarification. Firstly, why is the default availability model deployed to the same data center?

@mike-Ubezzi-MSFT please assign to @MashaMSFT
@anosov1960 for awareness

This thread seems to be causing some confusion so let me clarify.
First, the choice between RA-GRS, LRS and ZRS only applies to backup storage. RA-GRS enables the ability to restore from the read-only blob endpoint (geo-restore) even if the region goes down and you don't have database geo-replication set up. With zone redundant configuration the likelihood of the entire region going down is very small but it is not zero. Think of an event like hurricane, earthquake etc.  Plus, some customers require that data geo-redundancy is guaranteed as a matter of compliance. This is why it is the default is not changed for zone redundant databases. But you can certainly justify changing it to ZRS as a cost optimization decision, especially if compliance is not an issue. Pleas note, the self-service method to change the default is not yet released.

Hi @CeciAc and @Cedric-Bravo , please let us know if your questions have been answered? If so, we will proceed with closing out this Git issue. Otherwise, please let us know how we can help further?
Thanks!
Masha from the SQL Docs team

Hi @CeciAc  and @Cedric-Bravo , it's been some time since we've heard from  you so we'll assume your question was addressed and close out the Git Issue. Please let us know if there is anything more we can do for you.
Thanks and hope you both have a wonderful rest of your day!
Masha from the SQL Docs team
#please-close

authors: CarlRabeler CeciAc Cedric-Bravo MashaMSFT Mike-Ubezzi-MSFT anosov1960


text:
Any way to create these rules from commande line, either Powershell or az cli ?

I need to create a lot or similar alerts in different Log Analytic workspaces, doing everything from the portal is not automatable.

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

ID: 18f95793-d856-c29e-6d2c-d8145632898b
Version Independent ID: 98ae91ae-473c-f4da-a50a-a8ce432fa95a
Content: Create performance alerts by using Azure Monitor for containers
Content Source: articles/azure-monitor/insights/container-insights-alerts.md
Service: azure-monitor
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

Are you referring to Metric or Log Alerts?
For Metric Alert rules, you can wrap the Add-AlertRule cmdlet in a PS script: doc reference here
For Activity log alert rules, you can use Set-AzActivityLogAlert in a PS script: doc reference here.
We will now close this issue but don't hesitate to reply if needed.
Cheers,
Femi

source: gharchive/issue

authors: femsulu simon-michaud

repo: MicrosoftDocs/azure-docs

license_type: permissive

license_source: github-api


text:
broken link?

see this sentence:
For more information, see [Switch licensing model](virtual-machines-windows-sql-ahb.md

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

ID: 2a863cb0-c5d3-87d6-7c4d-28a1316d70f8
Version Independent ID: e56cf79c-d919-92d7-d3a0-05ada08ba17b
Content: Manage costs effectively for SQL Server on Azure virtual machines
Content Source: articles/virtual-machines/windows/sql/virtual-machines-windows-sql-server-pricing-guidance.md
Service: virtual-machines-sql
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@sasha-melamed Thanks for the feedback. I have raised a PR for fixing the broken link, the changes will be live once it is approved.

authors: VikasPullagura-MSFT sasha-melamed


text:
Azure Kubernetes cluster autoscaler switch issue

Azure documentation issue guidance
Hello,
Firstly Issue doc Link : https://docs.microsoft.com/en-us/azure/aks/cluster-autoscaler#create-an-aks-cluster-and-enable-the-cluster-autoscaler
Following the doc to create a cluster using the following command :
az aks create
--resource-group myResourceGroup
--name myAKSCluster
--node-count 1
--vm-set-type VirtualMachineScaleSets
--enable-cluster-autoscaler
--min-count 1
--max-count 3
Get issue screenshot as the following :

However, I've already created the autoscaler cluster a number of times by using the following command :
az aks create --resource-group myResourceGroup
--name myAKSCluster
--location northeurope
--kubernetes-version 1.15.3
--generate-ssh-keys
--enable-vmss
--enable-cluster-autoscaler
--min-count 1
--max-count 3

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

ID: 077f1bb5-2ba9-490c-2c6e-0de292266539
Version Independent ID: 0fd87b4f-88a4-c2eb-3ebc-f2b113ac203c
Content: Use the cluster autoscaler in Azure Kubernetes Service (AKS)
Content Source: articles/aks/cluster-autoscaler.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the feedback! We are currently investigating and will update you shortly.

@MicahMcKittrick-MSFT
This flag is available in Azure cli version 2.0.71 but not available in cloud shell Azure cli version 2.0.74
I believe this was removed in the latest CLI to favor the default value.

@cloudmelon I updated the doc to use the --enable-vmss command.
Once the PR merges the changes will go live after a few hours.


text:
Please specify that this is for a STORAGE ACCOUNT v2 and not BlobStorage or V1

as title, thanks

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

ID: badc419b-60d5-ba2c-0830-8d573db10dbe
Version Independent ID: efad89d0-d0da-895f-984d-046d67797ab4
Content: Tutorial: Host a static website on Blob storage - Azure Storage
Content Source: articles/storage/blobs/storage-blob-static-website-host.md
Service: storage
Sub-service: blobs
GitHub Login: @normesta
Microsoft Alias: normesta

@phil-lgr Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thank you @phil-lgr. I've added a note to the prerequisites that makes this requirement clear. That update will appear live by this afternoon. Thanks again!

#please-close

authors: Adam-Smith-MSFT normesta phil-lgr


text:
Private Endpoint vs. Service Endpoint

Need to add "Private Endpoint(s) are not permitted in conjunction with service endpoints in the same subnet"
https://docs.microsoft.com/en-us/azure/private-link/create-private-endpoint-portal

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

ID: bed2e199-b8cc-81d0-a739-b9acb46950bd
Version Independent ID: 7028bfc9-dd53-9a7a-b561-e7292e8aa055
Content: Connect privately to a storage account using Azure Private Endpoint
Content Source: articles/private-link/create-private-endpoint-storage-portal.md
Service: private-link
GitHub Login: @KumudD
Microsoft Alias: kumud

@gacurtin Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@KumudD Hi Kumud, could you please help check this issue and update the document as necessary ? Thanks.

added note to article
#please-close

authors: YutongTie-MSFT asudbring gacurtin


text:
How to update the load balancer sku from basic to standard?

I tried to add an IP restriction on an AKS LB with
az aks update \
    --resource-group rg-aks \
    --name myaks \
    --api-server-authorized-ip-ranges xx.xx.xx.xx/32

But got the error message:
Operation failed with status: 'Bad Request'. Details: Setting apiServerAuthorizedIPRanges [xx.xx.xx.xx/32] is not allowed with basic load balancer. Please recreate cluster with standard load balancer. Refer to https://aka.ms/aks/whitelist for more details

What the message suggested "recreate cluster with standard load balancer" is completely unacceptable for us (as well as for most of the running aks clusters I believe). But I could not find how to change the SKU from basic to standard without disturbing the running aks. Could you help me with if this is doable? If yes, how to do that? Many thanks!

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

ID: 60a7a0a8-97e7-0fda-763c-1a9972f4e9bc
Version Independent ID: 82b46441-43fc-fe48-97e2-0f3fca3d6eab
Content: Use a Standard SKU load balancer in Azure Kubernetes Service (AKS)
Content Source: articles/aks/load-balancer-standard.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

Thanks for the feedback! We are currently investigating and will update you shortly.

@tumluliu By default we now use the standard load balancer. However if you are looking to upgrade from Basic to Standard that is not possible and you need to rebuild the cluster

You can leave feedback requesting this functionality here: https://feedback.azure.com/forums/914020-azure-kubernetes-service-aks
But as mentioned, it is not possible at this time.
I will close this as no doc updated is needed. If you have further questions let me know.

authors: MicahMcKittrick-MSFT tumluliu


text:
Getting issue after deploying temperature analogy machine learning module in Ubuntu , run multiple instances of rsyslog, you need to specify different pid files for them azure ml

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

Status is running but when I log docker container it throws syslog fail to start as pod is already in used need

Hi @rahuljim - Thank you for your feedback. Since this channel is more for driving improvements towards MS Docs, could you provide us with a URL of the documentation that your feedback is most applicable to? That way, we're able to locate the right team that's better suited to address your feedback.

@rahuljim Just following up on my previous comment above, please let us know if you were following a specific MS Doc so we can correlate your feedback to the right team.

@rahuljim Since we haven't heard back, we'll proceed to close this issue for now. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

authors: mike-urnun-msft rahuljim


text:
Ran into problem trying to build the .war file

Terminal response is mvn: command not found.

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

ID: 264b32e3-9a21-233f-0056-b5bd970b47f2
Version Independent ID: 5e09b057-afba-d0a0-6fc0-94a78edd539f
Content: Tutorial: Java Enterprise app on Linux - Azure App Service
Content Source: articles/app-service/containers/tutorial-java-enterprise-postgresql-app.md
Service: app-service
GitHub Login: @JasonFreeberg
Microsoft Alias: jafreebe

Do you have Maven installed?

How can I check that I have maven installed?
On Mon, Dec 30, 2019, 10:41 PM Jason Freeberg notifications@github.com
wrote:

Do you have Maven installed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/45400?email_source=notifications&email_token=ALLRA2L3BZ27RQ36DGYVI33Q3LSRLA5CNFSM4KBS73Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH3ZTGA#issuecomment-569874840,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALLRA2IWW7FDV4UWTF3E4ILQ3LSRLANCNFSM4KBS73QQ
.

Here are the instructions to install Maven:
https://maven.apache.org/install.html
Can I ask why you're using Wildfly? Is this for work or for personal learning?

@yellowsmarty were you able to get Maven installed using the link provided by @JasonFreeberg?

I have maven installed, but I'm not sure if my Java home variable points my
to my JDK.
On Tue, Dec 31, 2019, 12:24 AM Jason Freeberg notifications@github.com
wrote:

Here are the instructions to install Maven:
https://maven.apache.org/install.html
Can I ask why you're using Wildfly? Is this for work or for personal
learning?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/45400?email_source=notifications&email_token=ALLRA2MBMR67GW3MADUI5RLQ3L6SXA5CNFSM4KBS73Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH34VKI#issuecomment-569887401,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALLRA2LKRANEBRMLOAG3763Q3L6SXANCNFSM4KBS73QQ
.

I'm trying to build a Java app with Azure. I'm just following the
documentation on the Microsoft website to get a better understanding of how
it works.
On Tue, Dec 31, 2019, 12:24 AM Jason Freeberg notifications@github.com
wrote:

Here are the instructions to install Maven:
https://maven.apache.org/install.html
Can I ask why you're using Wildfly? Is this for work or for personal
learning?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/45400?email_source=notifications&email_token=ALLRA2MBMR67GW3MADUI5RLQ3L6SXA5CNFSM4KBS73Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH34VKI#issuecomment-569887401,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALLRA2LKRANEBRMLOAG3763Q3L6SXANCNFSM4KBS73QQ
.

@yellowsmarty, I'm not a java expert by any means but I do have the following environment variables setup in my local machine.

I used chocolatey to install maven using choco install maven and my current version is 3.6.1.20190711.
Do you have the same values?


text:
App Consent Audit Workbook is missing

Description of the new workbook for "App Consent Audit" is missing.
There is no documentation available for this workbook.
Only the JSON and Workbook file exists on GitHub repo:
https://github.com/microsoft/Application-Insights-Workbooks/tree/master/Workbooks/Azure Active Directory/App Consent Audit
"What's new"-documentation references to this page without any further information.
https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/whats-new#september-2019

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

ID: eb2155a4-d8b2-a542-1aba-387183c3f2e3
Version Independent ID: 11565414-4093-d4cf-2665-1343b45a732a
Content: Azure Monitor workbooks for reports
Content Source: articles/active-directory/reports-monitoring/howto-use-azure-monitor-workbooks.md
Service: active-directory
Sub-service: report-monitor
GitHub Login: @MarkusVi
Microsoft Alias: markvi

I've created a backlog item to track this.
#please-close

authors: Cloud-Architekt MarkusVi


text:
Firewall Public IP address creation link

Can you please add a clarifying hyperlink at
Firewall deploy tutorial here at paragraph "Deploy the firewall" step 4. row here "Public IP address: Create new. The Public IP address must be the Standard SKU type."  a link to
Create new Public-ip address here ?
Thank in advance.

@ilyasOne Thank you for the valuable feedback,we are investigating the issue.

@ilyasOne The Public IP Creation described in the document you linked is different than the one for creating a new Azure Firewall, and creating a link here could be confusing.

However, instead of "Create New", it should state "Add New". I have made this change, and the doc should reflect it within 24 hours.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


text:
AcceleratedNetworking

Standard_E4as_v4 Vm supports Accelerated Networking?

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

ID: 8fdfbee1-bb47-fdfa-44f9-603b1313359e
Version Independent ID: 1404915e-3bca-00bf-a15c-b0545af47319
Content: Eav4-series and Easv4-series - Azure Virtual Machines - Azure Virtual Machines
Content Source: articles/virtual-machines/eav4-easv4-series.md
Service: virtual-machines
GitHub Login: @migerdes
Microsoft Alias: lahugh

@Vivekmis Thank you for your question! We will review and provide an update as appropriate.

Its supported.
Reference is here. https://docs.microsoft.com/en-us/azure/virtual-network/create-vm-accelerated-networking-cli#supported-vm-instances

@Vivekmis
I will close this out for now. If you need additional help please open a new issue.


text:
No mongo error on first npm start

When I executed 'npm start' for the first time after installing, I expected to see a Mongo error as per your documentation but it seems to have successfully connected to Database:        mongodb://localhost/mean-dev

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

ID: faff12d0-cc36-0867-a297-a8b59a863fdd
Version Independent ID: bbeb40cc-78e4-9c99-cdad-55f64a506c66
Content
Content Source
Service: cosmos-db

@michaeldunnOMM  Thank you for the valuable feedback. I forwarded your feedback to the content team.

#in-process

@michaeldunnOMM The error is expected at the initial run, I just tested it on my machine.  In your case there might be another instance of MongoDB running on your machine, and the app managed to connected to it. Let us know if you are blocked in further steps.

@michaeldunnOMM we will close this issue for now. In case you have further questions feel free to reopen the issue or create a new one.

#please-close


text:
Explanation of the Logs menu option is missing

When I provision a fresh app service it comes with a Logs menu option in the Monitoring section. But none of the provided tables are available by default. E.g. AppServiceAppLogs | take 5 throws the following error: 'take' operator: Failed to resolve table or column expression named 'AppServiceAppLogs'.
I believe there is a relationship with enabling the shipping of logs to a Log Analytics workspace. Can you shed some light?
Even after getting these tables available, they keep empty. What to do?

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

ID: bfc316af-0d30-b449-a04f-3019b7a16bc1
Version Independent ID: 01c4c435-fda9-374a-70b3-f1d7f13c7651
Content: Enable diagnostics logging - Azure App Service
Content Source: articles/app-service/troubleshoot-diagnostic-logs.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@cveld Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @cveld, thanks for your patience. Upon further review, we feel your feedback would be best received by the doc author to determine if an update to the current doc is necessary to align with your feedback.

#reassign:msangapu-msft

Haven't heard back from you. You'd have to configure the diagnostic setting if you're expecting logs in that table. See the tutorial here: https://docs.microsoft.com/en-us/azure/app-service/tutorial-troubleshoot-monitor#create-a-diagnostic-setting
#please-close

authors: BryanTrach-MSFT Grace-MacJones-MSFT cephalin cveld msangapu-msft


text:
Update provisioning job secrets via PowerShell/API?

We have this solution configured and working well for AWS Console access. For security, we'd like to be able to rotate the access key used by the IAM user created for provisioning (AzureADRoleManager in the tutorial).
I have been trouble finding documentation on a way to update the secrets for the provisioning job programmatically. I found a reference to a Microsoft Graph API in this doc (https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-configure-api). However, I was not able to locate an API reference for the  /beta/servicePrincipals/{id}/synchronization/secrets endpoint used in the example.
I played around with it in Graph Explorer but I wasn't able to tell how to retrieve the values for the current secret. I got something like the following:
{
    "@odata.context": "https://graph.microsoft.com/beta/$metadata#servicePrincipals('b9a2fcdb-fe85-4d17-979e-04e8a2c93652')/synchronization/secrets",
    "value": [
        {
            "key": "ClientSecret",
            "value": "*"
        },
        {
            "key": "SecretToken",
            "value": "*"
        },
        {
            "key": "SyncNotificationSettings",
            "value": "{\"Enabled\":true,\"Recipients\":\"[email address removed]"}"
        },
        {
            "key": "SyncAll",
            "value": "false"
        }
    ]
}

Without being able to retrieve the existing secret, that leaves us needing to store the current credentials elsewhere in order to use them to generate a new access key in AWS.
It would be really nice if automatic key rotation was integrated into the portal configuration. The provisioning user should be able to request a new key, update the secrets, then delete the old key after validation if given the appropriate IAM permissions.

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

ID: 8fa5814d-91e2-2f75-77e7-62a8597f340c
Version Independent ID: 458e93d7-a180-4c2f-5077-9b9d124d726a
Content: Tutorial: Azure Active Directory single sign-on (SSO) integration with Amazon Web Services (AWS)
Content Source: articles/active-directory/saas-apps/amazon-web-service-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@learley Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@learley This is the article which talks about USer Provisioning APIs https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-configure-api

#please-close

authors: SaurabhSharma-MSFT jeevansd learley


text:
Azure Function Keyvault SecretExpiring EventGridEvent

According to the documentation:
"Key Vault integration with Event Grid is currently in preview. It allows users to be notified when the status of a secret stored in key vault has changed. A status change is defined as a secret that is about to expire (within 30 days of expiration), a secret that has expired, or a secret that has a new version available. Notifications for all three secret types (key, certificate, and secret) are supported."
What does this mean exactly? If I subscribe to the SecretExpiring event, will my azure function be called only one time for any secret that will expire 30 days from the given date, or will the azure function be called every day until it expires.
We currently use a runbook to notify us of keyvault expiring secrets more frequently and wondering if switching to Keyvault EventGrid Notifications could replace our existing implementation in the runbook.
Anyone?

@alac0m Please help with the link of document on which above document feedback request is created.
Under this repository we want to make sure any issue is linked to a doc so we can help others that may be having the same issue.

@alac0m Please help with the link of document on which above document feedback request is created.
Under this repository we want to make sure any issue is linked to a doc so we can help others that may be having the same issue.

Thank you, I was referring the documentation provided here.
https://docs.microsoft.com/en-us/azure/key-vault/general/event-grid-overview

@AshokPeddakotla-MSFT Are you able to help answer this question?

@alac0m We have requested for an answer on this from the backend team and will update once we have it .

@alac0m it is incorrect statement. It should be 30 days before expiration. It is published just once.
I will update document.

Thank you @jlichwa

Thank you @jlichwa and @shashishailaj.
I would like to provide some feedback. It would have been great if we could specify the frequency of the expiring notifications starting from day 30 down to day 0. If that was possible, then we can replace our runbook implementation with this feature. As of now, we will not use this feature and continue using the runbook. Thank you!

@alac0m with current infrastructure we schedule events at creation. So can't just schedule 30 events every time. So without major change in infrastructure for events handling, it is impossible. Thank you

authors: AshokPeddakotla-MSFT alac0m jlichwa shashishailaj


text:
A security contact phone number should be provided for your subscription

[Enter feedback here]
The security center generated a compliance alert to register the contact phone, but I noticed that this field was removed from the notification option, but it still appears in the az security contact list command, the question is: is there a field for registration or is it false positive at the security center? shouldn't it be removed?

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

ID: 0a455a24-920e-f9f8-7a6f-60b5f4019acd
Version Independent ID: e6a4d8e2-0ada-e535-810f-5eb19e45ee1e
Content: Provide security contact details in Azure Security Center
Content Source: articles/security-center/security-center-provide-security-contact-details.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@jose-lima2011 Thanks for your feedback! We will investigate and update as appropriate.

@jose-lima2011 I am able to see the email contact list on the page and it is not removed.  Can you please share screenshot of your Azure portal ?

@jose-lima2011 I am able to see the email contact list on the page and it is not removed. Can you please share screenshot of your Azure portal ?

I think I didn't explain it correctly, the security center generates a non-compliance by CIS: 2.17.
Ensure that security contact 'Phone number' is set
This compliance was previously corrected in the phone field that no longer exists according to your printscreen. The question is: does this field exist? was it depreciated? if so why is the Security Center signaling this non-compliance?

see the image of the previous version in portuguese:

So again my question is about the phone field  not about email.

Having the same issue as stated above as well.

@jose-lima2011 Sorry about my confusion.  Yes, I see what you are talking about.  I am checking internally with the product team on this issue and update you as soon as I hear back from them.

@jose-lima2011  I have received the confirmation from product team that the field is still exist, but can only be set via PowerShell or API. For PowerShell use:
Set-AzSecurityContact -Name "default1" -Email "CISO@my-org.com" -Phone "2142754038" -AlertAdmin -NotifyOnAlert
For API use:
https://docs.microsoft.com/en-us/rest/api/securitycenter/securitycontacts/update

Thank you, but another question.  If a security contact already exists with a email address you want to add the phone number to I cannot find a method to just update the phone number.  I have tried to remove the contact then add it again and it fails the same saying the email address already exists even though it was deleted.

shaun findley, your question makes sense i had already seen this problem in fact i had flagged in a similar issue:
https://github.com/Azure/azure-cli/issues/14594
corrected without feedback, I add the question if the phone numbers are still restricted to the US format, I believe it shouldn't because the phone exists worldwide. Add the solution procedure in the System Center or I believe that many people will get lost in the correction

@shaunfindley  Yes, unfortunately, you need to pass both Name and Email even you want to setup Phone Number and it works as expected.

Also, I tried setting up Phone Number other than USA and it works as well.  See screenshot below -

@jose-lima2011 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


text:
WELL IT'S A START

[Enter feedback here]

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

ID: ea95f9c8-e0ad-93d2-cac2-0b486a684600
Version Independent ID: e03365fb-056d-1388-1cc3-01c009b1d2ec
Content: Advanced features of Azure Metrics Explorer - Azure Monitor
Content Source: articles/azure-monitor/platform/metrics-charts.md
Service: azure-monitor
Sub-service: metrics
GitHub Login: @vgorbenko
Microsoft Alias: vitalyg

@BertAnthonyRochester Thank you for reaching out to us on this channel.
Can you please share the additional information on your query so that we can assist you accordingly ? thank you .

@BertAnthonyRochester  Please note that this channel (the Azure Docs repository) is only for driving improvements related to the Azure documentation It would be great if you can specify what query you have with in the documentation, so that we can assist you accordingly.
At this point it appears that there's no further edits or updates needed to the documentation. We will go ahead and close this issue for now, however if you have any further queries please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


text:
Should use azure/webapps-deploy@v2 instead of azure/webapps-container-deploy@v1

A yaml file in Deploy to an App Service container uses azure/webapps-container-deploy@v1 as an action, however the action is deprecated. So the yaml should use azure/webapps-deploy@v2 instead. The following URL is the document of Azure/webapps-container-deploy and describe details of deprecattion  in the important notice.
https://github.com/Azure/webapps-container-deploy

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

ID: 850e4e1d-9648-243e-acde-39c4e9ef86a3
Version Independent ID: 1e24b051-b479-fb72-36f3-ef5a7d252bdf
Content: Custom container CI/CD from GitHub Actions - Azure App Service
Content Source: articles/app-service/deploy-container-github-action.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: jafreebe

@nakazax,  That's a good catch! Thanks for the feedback! We are taking a look into this and will get back to you soon.

Hi, I've opened PR #63100 for this issue.

@nakazax, Thanks for your contribution! Much appreciate you taking time to raise a PR on this. Your feedback has been shared with the content owner (@cephalin) for further review.

@nakazax @AjayKumar Thanks for flagging this. The latest version of the article uses webapp-deploy v2.

authors: AjayKumar-MSFT juliakm nakazax


text:
Metastore installation failing with metastore version 3.1.0

[Enter feedback here]
The metastore installation on SQL Server Database as backend fails as it tries to create tables with datatype VARCHAR(32676) which is not valid for SQL Server

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

ID: f0f84e4f-d0b5-d521-b003-f47cd475a090
Version Independent ID: 2208824e-e196-d80b-8d27-2b133061c43d
Content: External Apache Hive metastore - Azure Databricks
Content Source: databricks/data/metastores/external-hive-metastore.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@raunakjhawar Thanks for your comment. We will review the issue and get back to you shortly.

Hello @raunakjhawar  ,
SQL does not support VARCHAR(32676)  and hence you are getting the error , i think you will have to go with the varchar(max) .
Just tgo give you more perspective as to what will work and what now .
-- The below code works fine for any value which is less then 8000 . You can read more here
DROP TABLE TEST10052020
CREATE TABLE TEST10052020
(
COL VARCHAR(7999)
)
-- The below code fails , as you cannot have the value more then 8000
DROP TABLE TEST10052020
CREATE TABLE TEST10052020
(
COL VARCHAR(8001)
)
-- The below code works fine
DROP TABLE TEST10052020
CREATE TABLE TEST10052020
(
COL VARCHAR(MAX)
)
Thanks
Himanshu

Hello, I think that this issue should be reopened because the advice given doesn't help the initial poster. They have no control over the schema definitions because these are chosen by the Hive schema initialization code.
It seems that this is a bug in Hive and it also applies to the Hive schematool. During my most recent communications with MS Support, it was recommended to me that Metastores running on MSSQL be initialized by running migrations taken from the Hive source repository directly. I.e., for Hive 2.3.7, run the following file:
https://github.com/apache/hive/blob/master/metastore/scripts/upgrade/mssql/hive-schema-2.3.0.mssql.sql
That does solve the original poster's issue.
It would still be useful if the doc were updated to mention this. Also, that Hive 2.3.7 is the final 2.3.x version supported by the latest 7.3 LTS Databricks runtime. The current stable Hive release, 2.3.9, is not supported, and there are no plans to backport support to 7.3 LTS. It would be useful to note this, too.

authors: SwathiDhanwada-MSFT dbeswick-bupa himanshusinha-msft raunakjhawar


text:
No details on CosmosDB deletion/client setup for v3.x (Microsoft.Azure.Documents.Core)

I have been advised by support that to set up a singleton instance to CosmosDB in v3.x, I needed to use .Core instead of .Client. The new dependency compiles correctly, however I still dont have access to the DocumentClient class. I assume that I need to use a different class to access Cosmos, but I cannot locate documentation (nor could support)
Thanks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cb8d85a7-1ca3-71f4-85fb-7fb02850b60e
Version Independent ID: 3d7daee4-fd6d-0e96-299a-90b3637e6150
Content: Manage connections in Azure Functions
Content Source: articles/azure-functions/manage-connections.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@DraconInteractive Thank you for your feedback! We will review and update as appropriate.

@DraconInteractive Thanks for reporting this item! I have updated the doc and it will be published soon. We appreciate the feedback!

authors: DraconInteractive JayaChatterjee-MSFT


text:
Different key types not explained in detail

In the Index Access section it mentions using different types of keys. For example, "For end-user access, you can structure query requests to connect using a query key". The query key supposedly has READONLY. However, actually creating and using a query key isn't really obvious to me. If its in another part of the documentation I can't find it. It would nice to either elaborate on how to create and use different types of keys right in this doc, or to at least link to something that explains it from this doc.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cffc5753-1125-f6ee-de76-8ea460144c10
Version Independent ID: af3b7535-e78b-abb6-4a54-cdc55b6641bf
Content: Security overview - Azure Cognitive Search
Content Source: articles/search/search-security-overview.md
Service: cognitive-search
GitHub Login: @HeidiSteen
Microsoft Alias: heidist

@binbrain Thanks for the heads up! I'll add a link to the docs, but to unblock you right now, here are the steps: https://docs.microsoft.com/en-us/azure/search/search-security-api-keys

@binbrain  I added a link and the doc will be republished in a a few hours. Thanks for filing the issue!
#please-close

authors: HeidiSteen binbrain


text:
Azure Storage: "Only block blobs are currently supported."

Hello,
I noticed in this article, it states that "Only block blobs are currently supported". Whilst I understand that Data Share only supports the transfer to a "block blob" blob type to the target storage account, if the source storage account has page blobs, which are not leased, these are copied across to the target mapped storage account as block blobs, perhaps because the blob type is set in the Data Share execution code using the BlockBlobClient Class or using the REST API put block (myblob?comp=block) vs put page (myblob?comp=page).
The actual Binary Large OBject structure is still intact when copied using Azure Data Share. The target block blob can be copied from block blob type to a page blob type and then re-used e.g. for virtual machine disks.
I have tested this scenario and I was wondering if this could be updated in the article in regard to the supportability statement. Unless of course there are plans to support transferring page blob types as page blob to the target storage account via Data Share.
Thank you
Tejinder
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f56a647a-56d2-afad-8104-e34e20a8e063
Version Independent ID: b335cf24-8c6f-fdac-5158-d2eb36eb8c59
Content: Share and receive data from Azure Blob Storage and Azure Data Lake Storage
Content Source: articles/data-share/how-to-share-from-storage.md
Service: data-share
GitHub Login: @jifems
Microsoft Alias: jife

@tejinderrai  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@tejinderrai
We have updated the docs, and they should publish overnight. Thanks for raising this point! ~Jason

Thank you, that's very much appreciated.
Tejinder
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Jason Howell @.***>
Sent: Wednesday, 21 April 2021, 07:59
To: MicrosoftDocs/azure-docs
Cc: tejinderrai; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Azure Storage: "Only block blobs are currently supported." (#73369)
@tejinderraihttps://github.com/tejinderrai
We have updated the docs, and they should publish overnight. Thanks for raising this point! ~Jason
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/73369#issuecomment-823826766, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AD7FK4W4CHVIWFUSHEILRIDTJZZVXANCNFSM42QOVXJA.


text:
Alert details for VM_DataEgressArtifacts (App Services alert) is outdated

Alert details for VM_DataEgressArtifacts (App Services alert) is outdated (the alert title was incorrect and was corrected in the product).
Should be changed from:
Possible loss of data detected
(VM_DataEgressArtifacts)
to
Possible data exfiltration
(VM_DataEgressArtifacts)

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

ID: a2eb1ae9-1cfc-0dd0-a055-79ae32b62a6d
Version Independent ID: 66ce0f69-16aa-c1f8-5163-7cc5392a3399
Content: Reference table for all security alerts in Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/alerts-reference.md
Service: defender-for-cloud
GitHub Login: @memildin
Microsoft Alias: memildin

@tspivakms Thanks for the feedback! I have assigned the issue to the content author to evaluate and update the doc as appropriate.

Hi @tspivakms, thanks for the update.
I've changed the doc and the revised page will go live within 24hrs.
#please-close

authors: AshokPeddakotla-MSFT memildin tspivakms


text:
Code samples for MSAL net Client assertions are incorrect and outdated

Both exp and nbf should be numbers in the token, not strings.
manually creates RSACryptoServiceProvider which is superseded by certificate.GetRSAPrivateKey();

I'll try to submit a PR for this, if I manage to checkout this massive repository (Even Codespaces doesn't checkout the code correctly).

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

ID: fc3f2cc1-73e4-8d32-bd46-30a84e28f710
Version Independent ID: 4ccd0fa0-91de-4c53-6a63-3175a433a0df
Content: Client assertions (MSAL.NET) - Microsoft identity platform
Content Source: articles/active-directory/develop/msal-net-client-assertions.md
Service: active-directory
Sub-service: develop
GitHub Login: @jmprieur
Microsoft Alias: jmprieur

@svrooij
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@JamesTran-MSFT I already created a PR #86636 with a fix, there is the same author tagged. If that PR is accepted this issues is auto closed.

authors: JamesTran-MSFT svrooij


text:
Confused about the current version of Log Alerts API

In Upgrade to the current Azure Monitor Log Alerts API - Azure Monitor page, PowerShell cmdlets support is listed as one of the benefits.

However, the linked page says PowerShell is not currently supported in API version 2020-08-01, and it points to an Scheduled Query Rules API of version 2018-04-16.

Scrolling down a little bit, there is a sample use via Azure Resource Template link that brings me to a page which gives me an impression that 2020-08-01 is the current API version instead of 2018-04-16.

Scrolling down a little bit more again, in the process section, it says when switching to the current scheduledQueryRules API is successful the response should contain "version": 2.

My question is:

As of Jan 24, 2022 which one is the real current version of scheduledQueryRules API? Is it 2020-08-01, or 2018-04-16, or 2?

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

ID: 7494028f-bff6-47f0-0a32-e7627938d48b
Version Independent ID: 9adb3457-ec54-53a0-34a5-44cfb0706c11
Content: Upgrade to the current Azure Monitor Log Alerts API - Azure Monitor
Content Source: articles/azure-monitor/alerts/alerts-log-api-switch.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @yanivlavi
Microsoft Alias: yalavi

@dingliu Thanks for your comment. We will review the issue and get back to you shortly.

I submitted a change to this page to clarify it.
The current version of the API is scheduledQueryRules and it has two versions 2020-08-01 and 2018-04-16 both are GA.
This article is about migrating from the legacy rule management that used the log analytics API to scheduledQueryRules API.
To move from 2018-04-16 to 2020-08-01 you just need to touch the rule from 2020-08-01 and you will get the latest features. It is not a new API, only a new version.

#please-close

authors: SwathiDhanwada-MSFT dingliu yanivlavi


text:
Mobile Password-based apps section not correct

The section "Plan for mobile access" says the following:
For applications that use password-based SSO or accessed by using Microsoft Azure AD Application Proxy, you must use Microsoft Edge mobile. For other applications, any mobile browser can be used.
However, testing on my Samsung S10 after installing Mobile Edge App and navigating to our my apps URL, then clicking on an app that is password-based SSO, it opens a new tab but then immediately asks for the Intune Browser and takes me to the Play Store.
After installing, the Intune Browser then briefly prompts for the browser extension (like on a desktop), and then goes to the website, but then fails to pass the username password.
So there are multiple issues, but for this page, the statement is not correct that password-based works in Mobile Edge App.
I believe this needs updated to reflect what exactly is needed and how to make it work.
Thanks,
Eric

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

ID: 0e63fbf2-8107-91fa-ea13-d63b4000bab6
Version Independent ID: 2d10442b-0dd4-78b5-51a8-f182ee1ffdf1
Content: Plan My Apps configuration - Azure AD
Content Source: articles/active-directory/manage-apps/my-apps-deployment-plan.md
Service: active-directory
Sub-service: app-mgmt
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@rmwigdnal
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Updated the article with the following:
Be sure to enable password-based SSO in your mobile settings, which can be off by default. For example, Settings -> Privacy and Security -> Azure AD Password SSO.
#please-close

authors: JamesTran-MSFT davidmu1 rmwigdnal


text:
Import Key Vault Example should show Az command, not the deprecated command

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

ID: 36657265-6c54-f354-9e09-51f5f23d6ba5
Version Independent ID: bad1c0d1-b706-107a-3f15-e3e8d46b7e28
Content: Tutorial - Import a certificate in Key Vault using Azure portal
Content Source: articles/key-vault/certificates/tutorial-import-certificate.md
Service: key-vault
Sub-service: certificates
GitHub Login: @msmbaldwin
Microsoft Alias: sebansal

@JustinGrote
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Hi @JustinGrote, and thanks for your feedback.  I have updated this article, and it now references the Import-AzKeyVaultCertificate cmdlet (see https://docs.microsoft.com/en-us/azure/key-vault/certificates/tutorial-import-certificate?tabs=azure-powershell#import-a-certificate-to-your-key-vault). Good catch! #please-close

authors: JamesTran-MSFT JustinGrote msmbaldwin


text:
Question about https://docs.microsoft.com/en-us/azure/backup/backup-azure-vms-introduction#encryption-of-azure-vm-backups

At the referenced link in the article is the statement "When you back up Azure VMs with Azure Backup, VMs are encrypted at rest with Storage Service Encryption (SSE)." I wonder if "VMs are encrypted..." should be "VM backups are encrypted..." or "backups are encrypted..."?

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

ID: 2bdbfa0f-4305-1b2f-2dd9-a8c23e789a78
Version Independent ID: 7ceb2658-7fa8-3fbb-a9a6-81ddd40f4dd3
Content: About Azure VM backup - Azure Backup
Content Source: articles/backup/backup-azure-vms-introduction.md
Service: backup
GitHub Login: @v-amallick
Microsoft Alias: v-amallick

@brucelangston I think the phrase is correct. Look at the sentence used under support section. See the snippet below:

@brucelangston Checking in to see if the above answer helped. Let us know if there are still any additional issues we can help with.

@brucelangston We haven't heard back from you, so we will now close this issue. If this remains an issue, please reply and we will gladly continue the discussion.

authors: SadiqhAhmed-MSFT brucelangston


text:
Disabling Authorized IP Ranges Doesn't Work From Azure Cloud Shell Powershell

https://docs.microsoft.com/en-us/azure/aks/api-server-authorized-ip-ranges#disable-authorized-ip-ranges
Running the command specified here to disable auth IP ranges from Azure Cloud Shell returned an error:
az aks update --resource-group PII-RG --name PII-CLUSTER --api-server-authorized-ip-ranges ""
argument --api-server-authorized-ip-ranges: expected one argument
Examples from AI knowledge base:
az aks update --resource-group MyResourceGroup --name MyManagedCluster --api-server-authorized-ip-ranges 0.0.0.0/32
Restrict apiserver traffic in a kubernetes cluster to agentpool nodes.
az aks update --resource-group MyResourceGroup --name MyManagedCluster --load-balancer-managed-outbound-ip-count 2
Update a kubernetes cluster with standard SKU load balancer to use two AKS created IPs for the load balancer outbound connection usage.
https://docs.microsoft.com/en-US/cli/azure/aks#az_aks_update
Read more about the command in reference docs
Running the same command from Azure Cloud Shell Bash worked as expected for the customer but did not complete in a timely manner.
Please help fix this behavior from powershell, or update the documentation to reflect this issue.

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

ID: 660320d4-fad5-3307-e29f-5f4cfad4b7f7
Version Independent ID: 85ac2e8b-633f-6e1a-e642-0645ca92e129
Content: API server authorized IP ranges in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/api-server-authorized-ip-ranges.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

@reigntastic Thank you for your feedback!  We are reviewing the documentation and will get back to you shortly.

@reigntastic This is caused by a requirement in PowerShell for quote characters in a string.  In order for the double quotes to appear in the string, you'll need to enclose the entire string with something like single quotes:

@reigntastic We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Awesome, great find! Is the documentation updated to reflect that?
On Jul 15, 2022, at 1:16 PM, kobulloc-MSFT @.***> wrote:

@reigntastichttps://github.com/reigntastic This is caused by a requirement in PowerShell for quote characters in a stringhttps://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_quoting_rules?view=powershell-7.2#including-quote-characters-in-a-string. In order for the double quotes to appear in the string, you'll need to enclose the entire string with something like single quotes:
[image]https://user-images.githubusercontent.com/37556655/179285823-6b778906-64b1-4bb1-a182-6fbc01e02246.png
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/95719#issuecomment-1185786452, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQV477LOVCLLGTJR72BCHQLVUGTGNANCNFSM53PNZUDQ.
You are receiving this because you were mentioned.Message ID: @.***>

@reigntastic I've brought this up with the documentation team however it's a difficult issue to address.  While a number of people do stumble on this PowerShell requirement, there are a countless number of examples where you might encounter this.  Including a note for each instance may not be possible and it may rely on the reader to know this characteristic of PowerShell.

authors: kobulloc-MSFT reigntastic


text:
Updated PaaS to IaaS to reflect graphic

Updated PaaS to IaaS to reflect graphic.  Compute is traditionally referred to IaaS.

@JackStromberg : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.

Merging per email from Angela

source: gharchive/pull-request

authors: JackStromberg PRMerger16 ktoliver


text:
Updating Key vault certificate user role information

Updating certificate user role name and ID

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

Thank you for this, @felixtsem5. We will update our documentation with this revision -- we appreciate your contribution! #sign-off


text:
Update sql-data-warehouse-service-capacity-limits.md

Fixed SQL DW capacity limit for constants and identifiers in single expression.

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


text:
chore: Remove en-ca from support.microsoft.com url

To match link locale guidelines

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


text:
Fix typo

.Net -> .NET

Verified editorial correction.


text:
Change to not translate unique names

Same as #23964
An incorrect translation has been made in the localized version by machine translation.
※ Machine translation translates attribute name
Evidence: https://github.com/MicrosoftDocs/azure-docs.ja-jp/blob/live/articles\storage\blobs\storage-lifecycle-management-concepts.md
In the following files, it was made not to make mistranslation by putting proper names in "`".
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/role-based-access-control/custom-roles.md
This change(enclose parameter names by "`") has no negative effect on the English version.
Please accept this change so that parameter names are not mistranslated in each language in each localized version.
🙏

@changeworld : Thanks for your contribution! The author, @yzheng-msft, has been notified to review your proposed change.

#sign-off

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

@changeworld - Thank you for making this change.


text:
Extended support for gray scale dark style

#sign-off

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


text:
Typo "Azure container registry"→" Azure Container Registry"

https://docs.microsoft.com/en-us/azure/container-registry/container-registry-image-lock
#PingMSDFTDocs

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

Closing per #75369


text:
Update howto-create-users.md

Added additional info regarding table role which is very important. The info is also in attached postgres documentation but customers often miss it. This will help deflect support tickets on "how to give read/write access to a database for another user"

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

@ronzai Could you review the article author's feedback and make changes to your pull request accordingly? Thank you.

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


text:
Update os-coverage.md

adding missing word

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

#label:"aq-pr-triaged"

Thanks, @TomJanetscheck.
This was fixed in a separate PR. Please close.

authors: PRMerger16 TomJanetscheck ktoliver memildin


text:
Fix typo

/github action/i -> GitHub Actions

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

Thanks, @changeworld
#sign-off

authors: PRMerger14 changeworld craigshoemaker


text:
The last entry in the SAN list takes precedence over SN

The documentation should make this clear.
Please see:
https://github.com/Microsoft/BotBuilder-RealTimeMediaCalling/issues/2#issuecomment-303771297

Issue #2 has been closed in the samples repo.(https://github.com/Microsoft/BotBuilder-RealTimeMediaCalling).

authors: Kaiqb bogdan-mabo

repo: MicrosoftDocs/bot-framework-docs


text:
Bad design

Why src is not const char*?

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

ID: 7d63df7c-131f-66a2-cfba-78c584b4865a
Version Independent ID: 973598db-2ae7-fd75-e417-016052df59f4
Content: _swab
Content Source: docs/c-runtime-library/reference/swab.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @corob-msft
Microsoft Alias: corob

@satya-das
That's a philosophical question for the creator of the function. My guess is, it was created long before using const was a common software engineering paradigm for read-only data. The documentation accurately represents the declaration of the function, so I'm closing this issue.

authors: corob-msft satya-das

repo: MicrosoftDocs/cpp-docs


text:
Document exceptions to the rules for parsing C arguments

This description was empirically wrong, which made it rather confusing to read and rely upon. This is my best guess at the actual behavior, based upon some experiments, though I'm hoping the actual behavior will be documented based upon reading of the relevant codes themselves.
Note that this incomplete description was copied to other places, including:

https://docs.microsoft.com/en-us/windows/win32/api/shellapi/nf-shellapi-commandlinetoargvw
https://docs.microsoft.com/en-us/dotnet/api/system.environment.getcommandlineargs?view=net-5.0#remarks
https://github.com/dotnet/corefx/blob/b8b81a66738bb10ef0790023598396861d92b2c4/src/System.Diagnostics.Process/src/System/Diagnostics/Process.Unix.cs#L860

The CommandLineToArgvW function documentation also contains the misleading claim that "The GetCommandLineW function can be used to get a command line string that is suitable for use as the lpCmdLine parameter". This is not quite true, as the quoting/escape rules applied to argv[0] are usually different than those for the remaining arguments, so the user may want to first scan forward to the first space character not enclosed in double quotes.
Amusingly, dotnet also contains some contradictory advice to this existing documentation, but helpfully also gives a sample program that can be used to directly test in what ways it is non-conforming: https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.processstartinfo.arguments, and this seems to have lead to this other very long conversation about the many ways that this can and has caused problems: https://github.com/PowerShell/PowerShell/issues/1995

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

Note that others have observed that the behavior of this undocumented rule changed in VS 2008: https://daviddeley.com/autohotkey/parameters/parameters.htm#WINCRULES

@vtjnash
Thanks for taking the time to contribute. Your analysis and example aren't precisely right, but maybe some clarification is in order here.
There are several command-line parsing routines in use in Windows, and different apps use different ones. The Win32 API provides CommandLineToArgvW that behaves mostly like the C runtime startup, but may be different in some details. The C# startup uses yet another one. Documentation for one of these parsers doesn't necessarily apply to any of the others, so we won't discuss the differences.
The command line that a C or C++ program sees in its argv parameter may have been through two layers of parsing.
First comes processing by the command processor itself, which spawns the program process. It passes an environment, which contains a copy of the interpreted command line. It may have stripped out escapes from a batch file, or coalesced multiple lines, or streamed the command line in via a pipe. You have to read the docs on your command line processor to know what it might do before it hands off a command line to a spawned process. Different command processors may do different things. And a command processor isn't the only way a process can be spawned. Your app may have been spawned by a system call from another program, and the command line you get is up to that program.
Next comes processing by the runtime startup, which preps a bunch of things, including the argv parameter. The startup then invokes the entry point (main, winMain, etc.). The startup behavior code paths in the C runtime are slightly different for Windows apps, UWP apps, .NET C++ apps, and command-line apps, but for the kinds of apps we're describing in this article, the argv parsing behavior is the same. It's possible to replace the parser used by the runtime startup code with your own, if you like; there's even an object file you can link in to bypass argv setup completely. We'll ignore that for now.
The common command-line parsing routine used by the runtime startup code for console and Windows apps is available in source form in the Windows 10 SDK, under Source\<version>\ucrt\startup\argv_parsing.cpp. The main part of the parsing takes place in the parse_command_line function. A look at this code shows that it handles argv[0] separately with a simpler approach, based on the fact that it's constrained to be a valid file path. The later arguments get more complex handling.
Your example command line, a"b"" c d actually produces only one argument in argv[1], with content ab" c d. The reason is, the parser encounters the first double quote and enters in_quotes mode. When it finds the following "", it interprets this as an escaped double quote, which it outputs. It continues parsing in in_quotes mode, expecting a closing double quote, but it runs out of argument before it finds one, so it outputs that argument with the one double-quote character in it, then outputs the final nullptr to mark the end of argv.
I've updated the PR to reflect the behavior. Unfortunately, I touched enough that now your agreement to the license terms is required before I can merge it.

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

actually produces only one argument

I think it's worth noting that this is only true for VS2008 and later. For msvcrt-based applications (such as anything compiled by mingw-w64 or mingw32 or older applications such as python before 3.3 according to https://wiki.python.org/moin/WindowsCompilers#Which_Microsoft_Visual_C.2B-.2B-compiler_to_use_with_a_specific_Python_version.3F)

These documents are written to apply to VS 2015 and later, For VS 2008 and other out-of-support products, we provide access to the original docs under previous versions. Sure, it may be annoying if you're hoping for a one-stop shop for your Python 2.7 on mingw32 command-line argument parsing needs. But since 99% of readers are here for the most recent couple of versions of MSVC, we try not to slow them down with material that doesn't apply to them.

I just fear that it's still potentially misleading, since users may refer to this expecting to learn how to correctly launch an external program, and not realize that programs compiled by an older version of MSVC (such as python) may not follow these rules.

Just dropping back by again to record another another place in this repo I stumbled across, which had also copied the incorrect documentation from here: https://docs.microsoft.com/en-us/cpp/cpp/main-function-command-line-args?view=msvc-160


text:
note serialize does not sort.

The docs page does not explicitly state that no sorting occurs from the serialize operator.
More verbose description of "similar to extends" behavior in the [*Name2* = *Expr2*] syntax notes.
This follows from some confusion on my end implementing the operator. In the below example, I had previously assumed that serialize b, a would be the same as sort by b ,a
datatable(
    a: int,
    b: int,
    c: int
)[
    7,8,9,
    1,2,3,
    4,5,6,
]
| serialize b, a

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

@name Thanks for your feedback. This document has already been updated and includes a similar suggestion to the one you proposed. Because there is no change required, we're closing this issue.
#please-close

IMO the diff of the most recent update to this doc (d043cc9f2) does not appear to be a similar change to the one proposed here

authors: Court72 petervandivier shsagir

repo: MicrosoftDocs/dataexplorer-docs


text:
Text-only messages and tracking links

I just want to confirm the behavior of the tracking features with the text-only version of emails.
-The web beacon will not work at all?
-Redirect URLs are included as text, and if the recipient were to copy and paste that link into their browser it would still work (generate interaction data in Marketing).
-If you choose to edit the text-only version, this doesn't affect either of the points above (as long as you don't remove or edit the links).
Is that all correct? Thanks!

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

ID: b00817d3-332b-5fba-4de1-7bfd5e594f9b
Version Independent ID: 6c074f25-4977-bcef-b0c1-b55caef4af85
Content: Design, preview, check, and send marketing emails (Dynamics 365 for Marketing)
Content Source: ce/marketing/prepare-marketing-emails.md
Service: dynamics-365-marketing
GitHub Login: @kamaybac
Microsoft Alias: kamaybac

for details on feature functionality, please a support request describing the scenario, and details of the email records etc to affirm your exact scenario.

@dcbrown16 , those are interesting questions. Here are some answers:

Web beacon requires that the recipient loads images. Plain text means no images, so these opens won't be recorded. It's really up to the client (receiving) app and whether it loads the images, but I wouldn't expect so.
Links in the text version are replaced redirect links on send, so these will record as clicks if opened. (You'll only see these if you send the message using  a customer journey. The preview and all test sends don't show redirect links).
If you edit the text version, none of the above will change. You'll see final URLs for all links (not redirect links) while you're editing the text version, and any links you add to the text version (even if not also in the HTML) will be also parsed into redirect list when sent by a journey.

authors: dcbrown16 jain-shailesh kamaybac


text:
Create realtime-marketing-form-client-side-extensibility

Realtime form extensibility stub

@microsoft-github-policy-service agree


text:
Update readiness-bcall.yml

Added /bcsong under a new sub-heading "Just for fun" in the Social and Events box,

Thanks for this, much appreciated. We want to validate this with another team, so closing this PR for now and most likely pushing this from the private repo to live. Thanks!

authors: SusanneWindfeldPedersen andywingate


text:
samples

where are the sample codes on github? half of the links are dead, and github only have .md files without the code, where it is?

@MyTDT-Mysoft - could you please provide some specific pages (URLs for articles or readme.md files) to inspect?  Do you mean WebView2 samples, or samples for other technologies?
Are you rereferring to dead links in Readme pages at this main GitHub repo for WebView2 samples?
https://github.com/MicrosoftEdge/WebView2Samples/
I'm looking for dead links or missing sample code at or near these pages/URLs:
In the regular docs, the main, high-level page that links to articles about samples and links to the samples repo too:
https://docs.microsoft.com/en-us/microsoft-edge/webview2/code-samples-links
Location of Samples Repo 1 on GitHub:
The main WebView2 sample, which has many files other than .md:
https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/WebView2APISample
Location of Samples Repo 2 on GitHub:
A 2nd repo for WebView2 samples:
https://github.com/MicrosoftEdge/WebView2Browser
Microsoft's Samples Browser, which currently lists 3 of the WebView2 samples (the 3 are getstart completed tutorial projects):
https://docs.microsoft.com/en-us/samples/browse/

@MyTDT-Mysoft without more specific information from you on this, I'll have to close this issue. Feel free to comment back with more information and I can re-open it.

authors: MyTDT-Mysoft captainbrosset mikehoffms

repo: MicrosoftDocs/edge-developer


text:
after logon to technet i get some error msg

Hello,
i try to logon my account (it's not be use the last year) to technet forums
https://social.technet.microsoft.com/forums/en-us/home
after i try to type my user & password i get some error msg: "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
anyone can know how to fix it ?

@Computer24HR TechNet forums have closed at https://docs.microsoft.com/en-us/teamblog/msdn-technet-english-forums-closure

repo: MicrosoftDocs/feedback


text:
Extension doesn't add a UI in the toolbar and errors when running commands.

The extension isn't showing up in my version of vscode and if I run the Live Share: Launcher Setup command it throws the error "command 'liveshare.launcherSetup' not found".
I've tried disabling all other extension to be sure there isn't a conflict.  Not sure what else to try.
Thanks!
OS Version
Windows 10
Other version info

Here's the error in action.

@GollyJer Thanks so much for reporting this.
Unfortunately, we discovered this was an issue with this very latest VS Code Insiders update (it does not happen in stable).  We the details of this tracked as #182 and are hoping to get a fix out very soon along with some additional updates.
Thankfully, it does not repro in VS Code Stable.

Happens to me on OSX Sierra with VS Code version 1.16.0 (1.16.0) without insiders updates.

@mrozbarry Yes, that is a different issue - Visual Studio Live Share requires VS Code 1.20 or higher.  The latest is 1.22.2.  Update VS Code and you should be good to go.

@Chuxel updated to 1.22.2, uninstalled and reinstalled, still the same situation.

I don't see to have that category:

In the command palette, when I type live, I get no results.

@mrozbarry Okay, that means the extension is not initializing.  Restart Visual Studio Code, and go to Help > Toggle Developer Tools.  Do you see any errors in the "Console" tab?

Looks like uuid/v4 isn't being found:

Success, thanks for the help (and for piggy-backing on another similar issue).

@mrozbarry Great!
@GollyJer I'm going to close this issue as a duplicate of #182, but stay tuned as there will be an update shortly that should unblock insiders as well.

authors: Chuxel GollyJer mrozbarry

repo: MicrosoftDocs/live-share


text:
pagina web Academlo

Issue Type: Bug
proyecto 1 de academlo
Extension version: 1.0.2106
VS Code version: Code 1.45.0 (d69a79b73808559a91206d73d7717ff5f798f23c, 2020-05-07T15:57:33.467Z)
OS version: Darwin x64 19.3.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz (4 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
6, 6, 6

Memory (System)
8.00GB (0.08GB free)

Process Argv

Screen Reader
no

VM
0%

Thanks for reaching out. Can you give us more details about your scenario? 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.

Closing due to age. Please feel free to reactivate with more details so we can repro the problem!

authors: Davsterl aletsdelarosa pvergara242


text:
Update TOC.md

Category

[X] New article
Added article for Content Type Propagation

Docs Build status updates of commit 703f5df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/TOC.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

license: MIT


text:
TLS

This change to TLS instruction is too technical for the average home user of Office 365.
Please advise if Office 365 updates automatically changes your TLS

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

ID: 9ec089a7-8f7b-d4d9-a763-e8abd73fb2c9
Version Independent ID: 41ba8999-f0ea-5847-afad-8620dd83492a
Content: Disabling TLS 1.0 and 1.1 for Microsoft 365 - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/tls-1.0-and-1.1-deprecation-for-office-365.md
Service: o365-seccomp
GitHub Login: @WorkShay
Microsoft Alias: fasqiu

@woiim Thank you for your feedback. The effect on end-users is minimal. the change is basically to deprecate the protocol and start using the latest version. In case, if you have issues connecting to Exchange or any of the Microsoft services using applications like outlook, teams, etc, feel free to open a support case via the need help section in the M365 admin center and the support team will be able to assist you.
Hope this helps!
Thanks
Sri

authors: msbemba woiim


text:
Request for more context on how Alert Evidences gets created

Under the Microsoft Defender for Endpoint API section, the documentation describes the concept of Alerts. Alerts will have an evidence key to which the API will return related resources for a particular alert. I see that the evidence can and will be used in building a process tree. It would be nice if the community can get more clarification as to what is the criteria for choosing these particular records to be included in the evidence section in order to better understand the full potential when hunting for threats or building a graph for threat hunting purposes.

@Bexanderthebex Please indication which document you are referring to. Thanks

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!

authors: Bexanderthebex officedocspr5 yogkumgit


text:
update ToC

The Table of Content (ToC) does still state twice 'What is EOP?' while the article is titled as 'What is Exchange Online Protection (EOP)'. The ToC should be updated so it's clear what it is about without opening the article.

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

ID: 14130f97-cb6e-999d-c2c8-47ef1d7bfff8
Version Independent ID: 4511a0e0-4616-c882-a420-13f4b59ce88b
Content: What is EOP - Office 365
Content Source: microsoft-365/security/office-365-security/what-is-eop.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@giant, I only see one reference in the TOC file, and in search results for "What is EOP?

I guess we must have fixed it?
Thanks for the feedback.
Closing

@chrisda I see the same behavior but if you check that one article the ToC entry doesn't match the article's title. So this should be updated too.

authors: GiantCrocodile chrisda


text:
Problem with a column in one place

Hello!
The document needs a small change to the formatting in this part:
SFV:SFEFiltering was skipped and the message was allowed because it was sent from an address in a user's Safe Senders list.
For more information about how admins can manage a user's Safe Senders list, see Configure junk email settings on Exchange Online mailboxes.
The text needs to be moved to the next cell.

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

ID: e47e11dd-53ab-5f62-ac6c-59dbc00eed0d
Version Independent ID: 362ad038-3b64-f342-2f8e-111635c4337d
Content: Anti-spam message headers - Office 365
Content Source: microsoft-365/security/office-365-security/anti-spam-message-headers.md
Service: o365-seccomp
GitHub Login: @chrisda
Microsoft Alias: chrisda

@Kajt90, I fixed it: |SFV:SFEFiltering... to |SFV:SFE|Filtering....
Thanks for the feedback.
Closing

Thx, have a great one!
pt., 23 paź 2020, 19:12 użytkownik Chris Davis notifications@github.com
napisał:

@Kajt90 https://github.com/Kajt90, I fixed it: |SFV:SFEFiltering... to |
SFV:SFE|Filtering....
Thanks for the feedback.
Closing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3255#issuecomment-715436910,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARPSJEILT2UV6CQXFC3FQZLSMGTPBANCNFSM4S4O2KKA
.


text:
No update on the changes over New Exchange Admin center

I certainly enjoy the change but few thing they are considering that compliance portal can handle but i guess they are far behind to give that feature available through changes.
One of the important feature i am considering here is Retention tags, and I strongly believe this feature should not be remove.

from https://docs.microsoft.com/en-us/exchange/security-and-compliance/messaging-records-management/default-retention-policy
They say Retention policy from compliance center should take care of it from here. But i strongly disagree. There is no option to create tag on the basis of folders, No labels for moving data into archives after certain period.
MRM is not part of legal compliance, Team has to understand that it is always the part of Mailbox Hygiene and should still be there.
In this specific article they are not even talking on how to handle 3 year, 4 year and 5 year move to archive through new portal updates be it be Exchange admin center or Compliance portal.
Please suggest! how we can achieve?
~Yash from CloudNerdy
yash@cloudnerdy.onmicrosoft.com/yashbhilware@hotmail.com

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

ID: 81e9c1f9-d22d-8c83-25bb-637f3121ef33
Version Independent ID: b6c1f57d-978f-c959-ef0a-00ef1b9d9cab
Content: Set up an archive and deletion policy for mailboxes in your organization - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/set-up-an-archive-and-deletion-policy-for-mailboxes.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

@yashbhilware Thank you for your feedback.

You should continue using MRM to move messages to archive mailboxes as the feature is not available yet in the New exchange admin center or compliance center. Once the feature if available, you will see that added to the document.

Retention labels can be applied on folder level in outlook -https://docs.microsoft.com/en-us/microsoft-365/compliance/create-apply-retention-labels?view=o365-worldwide#manually-apply-retention-labels

The recommendation is to use retention policy and retention labels from the compliance center for proactive deletion or retention as this is a single mechanism to control the content across Microsoft 365. Also, note that MRM will continue side by side with the retention policy and labels as mentioned in the document.
Hope this helps!
Thanks
Sri

authors: msbemba yashbhilware


text:
Additional documentation linked

Documentation with current Intune network endpoints added

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

acknowledged review

@hathin - please merge the commit on the copy/edit review done by JohanFreelancer9 or make the necessary changes on the PR following the suggestions made. Thank you.

@jaimeo - PR has been copy edited and is ready for final review.
Thank you.
cc: @kenwith

authors: hathin mypil


text:
added requirement for ATP

#689

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@MSFTTracyP - PR has been copy edited and is ready for final review based on issue #689.
Thank you.
cc: @kenwith

Hello @AntoineJo ,
Thank you very much for the provided information.
Dear @MSFTTracyP , could you please confirm?
Thank you

@MSFTTracyP - We would like to follow up on this. Can you please share your insights on this?
Thank you.

authors: MaratMussabekov mypil


text:
Update configure-exchange-server-for-hybrid-modern-authentication.md

added more clarity in Note for Domain Name parameter

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

approved copy review suggestions.

@kelleyvice-msft Please merge this PR. Thanks

authors: mukeshHCW yogkumgit


text:
Update ios-install.md

Removed Duplicate steps on enhanced Anti-phishing capabilities,

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/7382

@mjcaparas Please merge this PR. Thanks

authors: msbemba yogkumgit


text:
CI Update

Build.Reason:Manual by Alma Jenks
Build.Url:https://apidrop.visualstudio.com/Content CI/_build/results?buildId=252256&view=results
source_repo.branch:master
source_repo.csvPath:bundlepackages/mipsdk-dotnet
source_repo.url:https://apidrop.visualstudio.com/binaries/_git/mrefconfig

Docs Build status updates of commit 449ee41:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy.Actions/ActionType.xml
:bulb:Suggestion
View
Details

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy.Actions/JustifyAction.xml
:bulb:Suggestion
View
Details

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy/ExecutionState.xml
:bulb:Suggestion
View
Details

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy/IPolicyEngine.xml
:bulb:Suggestion
View
Details

mipsdk-dotnet/xml/FrameworksIndex/mipsdk-dotnet-1.10.xml
:white_check_mark:Succeeded

mipsdk-dotnet/xml/FrameworksIndex/mipsdk-dotnet-1.9.xml
:white_check_mark:Succeeded

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/AccessDeniedException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/AdhocProtectionRequiredException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/BadInputException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/ConsentDeniedException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/ContentFormatNotSupportedException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/CustomerKeyUnavailableException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/DelegateResponseException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/DeprecatedApiException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/FileIOException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/InsufficientBufferException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/InternalException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/JustificationRequiredException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/LabelDisabledException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/LabelNotFoundException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/LicenseNotRegisteredException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/NetworkException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/NoAuthTokenException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/NoPermissionsException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/NoPolicyException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/NotSupportedOperationException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/OperationCancelledException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/PrivilegedRequiredException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/ProxyAuthenticationException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/ServiceDisabledException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/TemplateArchivedException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Exceptions/TemplateNotFoundException.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/BodyType.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/FileEngineSettings.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/FileExecutionState.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/FileHandler.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/FileProfileSettings.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/IFileEngine.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/IFileHandler.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/IFileInspector.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/IFileProfile.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/IFileStatus.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/IMsgAttachmentData.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/IMsgInspector.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/InspectorType.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/LabelingOptions.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/PFileExtensionBehavior.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.File/ProtectionSettings.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy.Actions/Action.xml
:white_check_mark:Succeeded
View

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy.Actions/AddContentFooterAction.xml
:white_check_mark:Succeeded
View

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

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy.Actions/ActionType.xml

Line 0, Column 0: [Suggestion-ECMA2Yaml_Enum_NoRemarks] Please note: <remarks> node on Enum fields will be ignored.

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy.Actions/JustifyAction.xml

Line 0, Column 0: [Suggestion-disallowed-html-tag] HTML tag 'seealso' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy/ExecutionState.xml

Line 0, Column 0: [Suggestion-disallowed-html-tag] HTML tag 'example' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 0, Column 0: [Suggestion-disallowed-html-tag] HTML tag 'example' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.

mipsdk-dotnet/xml/Microsoft.InformationProtection.Policy/IPolicyEngine.xml

Line 0, Column 0: [Suggestion-disallowed-html-tag] HTML tag 'param' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.

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/mipsdk-dotnet