Redirecting to Classic Portal Instead of New Portal in Microsoft Purview
I am using the following endpoint in my Python script to create new terms in the Microsoft Purview New Portal: purview_endpoint = "https://api.purview-service.microsoft.com" However, this endpoint redirects me to the Classic Portal instead of the New Portal. Has anyone encountered this issue or knows how to resolve it? Thanks in advance!Navigating Azure WAF Exclusions
Exclusions in Azure WAF (Web Application Firewall) are a critical feature that allows administrators to fine-tune security rules by specifying elements that should not be evaluated by WAF rules. This capability is essential for reducing false positives and ensuring that legitimate traffic flows unimpeded. Exclusions are designed to fine-tune the WAF’s sensitivity, allowing legitimate traffic to pass through while maintaining robust security measures. They are particularly useful in scenarios where certain request attributes, such as specific cookie values or query strings, are known to be safe but might trigger WAF rules due to their content or structure.
Purview API: When can a DataSet have many attachedSchema?
In the definition of a DataSet, there is a relationshipDef for attachedSchema that supports more than one schema. In what scenario would there be more than one attached schema for a single data set? I am trying to extract the schema for an azure_datalake_gen2_resource_set based on a delta table. I have been just using the first attachedSchema in the returned list, but am wondering if that is safe to do. Definition of the relationship: { "name": "attachedSchema", "typeName": "array<schema>", "isOptional": true, "cardinality": "SET", "valuesMinCount": -1, "valuesMaxCount": -1, "isUnique": false, "isIndexable": false, "includeInNotification": false, "relationshipTypeName": "dataset_attached_schemas", "isLegacyAttribute": false }` Example of what is returned from the purview API (when could there be more than one entry in the "attachedSchema" list?): { "entity": { "typeName": "azure_datalake_gen2_resource_set", "relationshipAttributes": { "attachedSchema": [ { "guid": "guid", "typeName": "parquet_schema", "entityStatus": "ACTIVE", "displayText": "parquet_schema", "relationshipType": "dataset_attached_schemas", "relationshipGuid": "relid", "relationshipStatus": "ACTIVE", "relationshipAttributes": { "typeName": "dataset_attached_schemas" } } ] } } }Securing App Secret
Raviv Tamir In the blog post https://techcommunity.microsoft.com/t5/Microsoft-Defender-ATP/WDATP-API-Hello-World-or-using-a-simple-PowerShell-script-to/ba-p/326813 the API call to create a token to configure a connection to ATP. The issue at hand is that the line $appSecret = '' ### Paste your own app keys here is all in clear text. We have issues with that in a script. Is there a way to secure that information so when someone looks at that script, they will not be able to attain all of the information needed to create that access token?
