Ondersteuning van de Azure-community
Stel vragen, krijg antwoorden en kom in contact met Microsoft-technici en experts in de Azure-community
Kennismaking met Azure op Q&A
Vind antwoorden op uw technische vragen over Azure-producten en -services. Kom in contact met Microsoft en deskundigen in de community, wissel feedback uit en leer van anderen. Het MSDN-forum wordt vervangen door Azure op Q&A op de website van Microsoft Q&A. Maar u kunt nog steeds in de forumarchieven zoeken.
Antwoorden van Microsoft en de community op oudere technische vragen over Azure
Forum: Azure Networking (DNS, Traffic Manager, VPN, VNET)
Forum: Azure N-Series Virtual Machines
Forum: Microsoft Azure Site Recovery
Forum: Azure Active Directory
De community reageert op ontwikkelingsvragen
De community reageert op systeem-/netwerkbeheerdersvragen
Ideeën of suggesties plaatsen met betrekking tot uw ervaring met Azure
Please enable AZ support in UK West region as well
Issue:Storage accounts offer several methods of granting access to the data, such as Storage Account Keys, Shared Access Signatures, RBAC roles such as Storage Blob Data Contributor, Access Control Lists. In scenarios where RBAC or ACLs are used, the option to easily access the account keys and generate SASs for storage account owners pauses an unnecessary security risk, since these short password-like strings can easily be stolen by just writing them down.Proposed solution:The ARM template is extended with an optional field to disable Account Keys and SASs for the storage account, leaving only RBAC and ACSs as authorization options. Once this is set during storage account creation, the flag becomes immutable, so that in case it ever needs to be changed after creation, the only way is to create a new storage account and copy the data.
Address:328 Greenbrook Rd Suite 4Green Brook Township, NJ08812Phone:(732) 667-7805Website:https://lisa-day-spa-asian-massage-open.business.site/Description:Here at Lisa Day Spa we are massage therapists trained to provide all kinds of massages in one place!Keyword:Massage spa in Green Brook Township, New Jersey, Shiatsu, Deep Tissue, lymphatic detoxificatio, Swedish, Asian Staff, Private Rooms, Asian Spa, Foot Massage, Couples Massage, Four Hands, Private Rooms, Back Door Entrance, Hot Towels, Hot StonesHours:Mon to Sun 9:30 AM to 9:00 PM
We have Guest Agent set as auto-update, as of today we do not know which is latest and if auto-update succeeds or fails unless we open a case with support and understand. We need something in a dashboard if agent auto-update is succeeded or failed and is in line with the latest version
After February 1st 2010, it's going to be tough for developers/freelancers/hobbiest to learn, test and deploy azure applications as it's going to be billed for everything. Like Google AppEngine (http://code.google.com/appengine/whyappengine.html#norisk) Azure should provide free offering for developers with some similar limitations and if the usage goes beyond, one can enter in billing.
The option of using Azure Data Factory v2 to migrate data to the Power Platform / CDS / D365 is good, although there are a few features that are missing that almost negate considering the tool as a viable option. Two such examples are:-1. You cannot write to the createdby field on any entity as the createdby is always set in the context of the user in the Linked Service and does not respect the data that is passed to it as part of the Sink data source2. There is no way to migrate data into the native CDS / D365 many-to-many entities (aka mapping table / entity), despite these only consisting of 3 fields (a unique ID and the 2 Foreign Keys of the related entities).3. No support for PartyList type fields
When you create a custom error page in Application Gateway, the storage blob stored the error page file needs to be accessible publicly now.It would be nice to be able to limit access to the storage blob so that we can make sure our data is secure.
I want to transfer a client certificate to the backend with Azure Front Door.However, Azure Front Door doesn't support the SSL passthrough function.I would like to support transferring the client certificate used in the TLS session established between Azure Front Door and the client to the backend.
For now,when customers want to disassociate WAF policy from Application Gateway,we have to change Application Gateway from WAF SKU to Standard SKU.When we changed to Standard SKU,system can be exposed to threats.Please redesign this just like that disassociating WAF policy from listener.